Ask or act: tool availability dissolves the visibility-clause tax

Ask or act

Tool availability dissolves the visibility-clause tax

The Open Exposure

Study AG left one exposure open: under outline views, the shipped ask rule converted fully specified edits into NEED-INFO about 70% of the time, because the target node was "not visible"; even with the last-edit echo supplying id, key, and both values. AN re-ran that construction with a get_template_view tool in hand, four arms, three models, 1,728 session steps.

Availability Settles It

Availability alone settled it: anaphora success rose to 45–48/48 with essentially zero asks on every tier, models fetching at most one or two precise views or patching directly from the echo.

Unsafe Below the Frontier

The registered "prefer fetching over asking" clause added nothing where tools existed; and the protection arm showed it is unsafe below the frontier: told to prefer tools, sonnet silently guessed half of its genuinely unanswerable cells and gemini burned 689 tool calls hunting the conversation-borne referent in the tree, while opus asked a perfect 48/48.

The Fence

The clause stays unshipped; the fence is capability-shaped: give tool-bearing surfaces the ask rule freely, and never pair the rule with skeleton views on a surface that lacks the tools.