click

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

The readOnlyHint=false annotation already signals a mutating operation, and the description adds no behavioral context such as possible navigation, dialog triggers, or snapshot refreshing. With no output schema, the agent gets no insight into side effects or return behavior beyond the boilerplate 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 one short sentence with no redundant filler and the verb is front-loaded. It is concise, though slightly too terse to convey the optional double-click and snapshot behavior.

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 simple click operation, the schema covers parameter mechanics and the description states the action, which is minimally viable. However, the lack of side-effect disclosure, alternative routing, and return-value guidance leaves meaningful gaps for an agent deciding whether to invoke it.

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 the parameters are already documented in the structured schema. The description adds only the vague phrase 'provided element' and doesn't enrich the meanings of pageId, uid, dblClick, or includeSnapshot, so it stays at the baseline.

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 states the action ('Clicks') and the target ('provided element'), which is clear at a basic level and distinct from navigation or page-management siblings. However, it doesn't distinguish click from related interactions like hover or drag, and 'provided element' doesn't mention that the element must come from the snapshot uid.

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?

There is no guidance on when to use click versus sibling tools such as hover, drag, type_text, or press_key. The dblClick parameter exists in the schema as an alternative interaction mode, but the description doesn't mention it or any exclusions.

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