batch_click

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

With no annotations, the description clearly discloses error handling ('Continues on error') and independence of clicks, which is critical behavioral context. However, it does not mention potential side effects like navigation or schema-imposed limits (max 10 clicks), though the maxItems constraint is in the schema.

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?

The description is three concise sentences, front-loading the main action and then adding key behavioral details. Every sentence earns its place without unnecessary elaboration.

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 tool with three parameters (one a complex array) and no output schema, the description covers core behavior but leaves ambiguity about the return structure. 'Returns per-click results' is vague; specifying the result format (e.g., success boolean, error string) would make it more 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 coverage is 100%, providing clear descriptions for each parameter. The description adds value by explaining the sequential and independent behavior across the 'clicks' array, which helps agents understand how parameter values interact. It does not elaborate on individual parameter selection (e.g., ref vs. selector), but the schema already covers that adequately.

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 verb 'Click multiple elements sequentially', which precisely communicates the action and resource. It distinguishes itself from the sibling 'click' tool by indicating batch processing with independent errors and per-click results.

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 implies use for multiple independent clicks but does not explicitly compare to the sibling 'click' tool or state when to use alternatives. No 'when not to use' guidance is provided, leaving some ambiguity for an AI agent.

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