Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, but the description adds real context beyond them: the confidence-threshold operating loop, the return-on-uncertainty/blocked behavior, the no-model short-circuit, and the Chrome approval pause for risky actions. It stops short of describing the shape of what comes back on success.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core action and free of filler; the behavioral caveats are grouped at the end where they belong. The second sentence is somewhat run-on, but every clause contributes operational information rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world mutation tool with no output schema, the description covers the safety and control-transfer story well but omits the return payload on success and all parameter semantics, including the observation_mode/observation_scope enums an agent must set to call it correctly. Adequate, but with a clear parameter-level gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, so the description carries the full burden, yet it never explains subgoal, task_id, skill_id, max_steps, success, observation_mode, or observation_scope. Only a loose hint ('bounded subgoal', 'the task's sites and permissions') touches the schema at all, leaving two enums and the step limit undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific actor (BrowserPair Reflex), a verb (give a bounded subgoal to carry out), and a scope (in the user's browser). An agent can tell this delegates autonomous browser work rather than, say, observing state. It does not, however, distinguish itself from the sibling browser_run, which is the most likely confusion point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It routes the agent forward in one case (when no Reflex model exists, continue with task_respond) and explains when control is returned, which is useful implied guidance. It gives no explicit rule for choosing task_subgoal over alternatives like browser_run or browser_list, so the main selection decision is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.