Click element

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is largely covered. The description adds that it returns the new snapshot and is useful for expanding sections, but it does not disclose potential side effects of clicking, failure behavior, or what the snapshot contains.

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 tight sentences with the core action front-loaded and no wasted wording. The prerequisite and return behavior are stated efficiently.

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?

Covers the main prerequisites, action, return value, and typical use case. Given that annotations declare readOnly/openWorld and the schema fully describes parameters, it is largely complete, though it omits failure handling and snapshot contents.

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 all five parameters are documented in the schema. The description reinforces the text-vs-selector identification mechanism but adds no detail beyond the schema for nth, waitMs, or saveCaptures, so baseline 3 is appropriate.

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?

States a specific verb and resource: click an element on a page opened with open_page, using visible text or CSS selector, and returns a new snapshot. It clearly distinguishes itself from open_page by naming it as the prerequisite, though it does not explicitly differentiate from the sibling download_by_click.

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?

Gives a clear use case (expanding sections of a web app) and labels the tool as advanced, implying caution. It does not state when not to use it or explicitly compare it to alternatives like download_by_click.

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