scout_click

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

With no annotations provided, the description carries the full burden. It discloses that clicking returns a healer result, may cause navigation (rendering IDs stale), and that force bypasses overlay interception. However, it does not explicitly state potential side effects like page navigation or data changes beyond mentioning navigation as a possible state change.

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?

Three sentences, each providing essential information without redundancy. The description is front-loaded with the primary action, followed by return value, then usage condition and force parameter explanation.

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?

The description covers key aspects: action, return value, stale ID handling, and force parameter. While it doesn't explicitly mention prerequisites (e.g., needing a snapshot), it is implied by 'snapshot ID'. For a tool with no output schema and moderate complexity, it is sufficiently complete.

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 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that 'id' is an element ID from the last snapshot, and 'force' bypasses overlay interception for shadow DOM or modals. This enhances understanding.

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 clearly states the tool clicks an element by its snapshot ID and returns a healer result. It distinguishes itself from sibling tools like scout_drag, scout_hover, etc., by specifying the action and result.

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?

The description provides explicit guidance on when to use force=true (shadow DOM, modals) and warns that if stateChange is 'navigation', element IDs become stale and require a new snapshot. This helps the agent decide when to use the tool and when to call scout_snapshot instead.

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