click

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

Without annotations, the description fully discloses the two behavioral paths (click only vs click+follow navigation) and the return values in each case. 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 sentences with no wasted words. The first sentence states the action and parameter, the second explains the two outcomes. Perfectly front-loaded.

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?

Given the complexity of two scenarios and a side-effect (navigation), the description is complete. It covers both return cases without needing an output schema.

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 single parameter 'ref' is described in the schema as 'Element ref like e:142'. The description adds context ('returned from query') and clarifies its origin. Since schema coverage is 100%, baseline is 3, and the addition justifies a 4.

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 it dispatches a click event on an element referenced by ref, and distinguishes between <a href> navigation and other elements. It is specific and differentiates from sibling tools like activate or submit.

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 explains when auto-navigation occurs (for <a href> without preventDefault) and implies general usage for clickable elements. It doesn't explicitly exclude non-clickable elements or mention alternative tools, but provides good context.

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