click

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

With no annotations, the description carries full burden and discloses that clicking returns cleaned content, that re-returning the full page is wasteful on stateful pages, and that waiting is needed for client-side fetches to avoid early reads. This provides useful operational context beyond the basic action.

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 densely informative, with each sentence adding meaningful guidance and examples. It is well-structured, starting with the main action and then providing scenario-based refinements for stateful pages and client-side fetches.

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 output schema and the tool's complexity, the description provides sufficient context for correct invocation, covering return content scoping and async waiting. The only minor gap is `timeout_ms`, but the overall guidance is comprehensive.

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 description explains the meaning and use cases for `selector`, `result_selector`, `wait_for_selector`, and `wait_for_idle`, critical since schema coverage is 0%. However, `timeout_ms` is not addressed, leaving its semantics to inference.

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 CSS selector and returns the resulting page's cleaned content, which distinguishes it from navigation and extraction siblings. The specific verb 'Click' and resource 'element by CSS selector' make the purpose unmistakable.

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 `result_selector` (stateful pages) and `wait_for_selector`/`wait_for_idle` (client-side fetch), with concrete examples. However, it does not explicitly contrast with alternatives like `navigate`, though the mention of 'navigate' implies a sibling relationship.

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