click_at

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

Beyond the destructiveHint=false annotation, the description discloses the coordinate-based clicking behavior and the effect of returnSnapshot returning a fresh snapshot with renumbered refs. No contradictions.

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?

Two concise sentences, front-loaded with the core action and immediately followed by a specific use case. No unnecessary words.

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 tool is simple; the description covers the key use case and parameter effect. No output schema, but returnSnapshot hints at output. Could mention potential navigation or page changes from clicking, yet still sufficient.

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?

The tool description adds no meaning to x and y beyond what the schema already indicates (coordinates). With only 33% schema coverage, the description should compensate but does not. returnSnapshot is already documented in schema.

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?

Clearly states verb (click), resource (page coordinates), and distinguishes from sibling tools by specifying it clicks at coordinates rather than on elements. The use case for cross-origin iframes further clarifies purpose.

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?

Describes when to use (for controls in cross-origin iframes not enumerable by snapshot), but does not explicitly mention when not to use or list alternatives. Still provides clear context for selection.

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