click

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

Discloses key runtime behavior beyond the schema: a fresh stateless browser context, waiting after load, DOM click implementation, possible navigation, and response read after navigation. Also documents the clicked:false miss case. Since there are no behavioral annotations, this description carries the burden and does so thoroughly.

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?

Four dense sentences with no filler; the main action comes first, then side effects, error case, and alternative are sequenced for efficient parsing. Every sentence earns its place.

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 three simple parameters, the description covers statelessness, clicking behavior, navigation, and the no-match return value. It is nearly complete, but without an output schema it leaves the exact success shape implicit beyond url/text_after and clicked:false.

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%, so the baseline is 3. The description adds semantics on top: the selector matches the first element, wait_secs governs time after page load before clicking, and url is loaded in a fresh context. This extra context justifies a 4 rather than 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?

States a specific operation ('Click an element on a one-off page') with a clear resource (the page URL) and mechanism (CSS-selector match). It explicitly contrasts itself with session_click, so an agent can distinguish it from sibling click tools without inferring.

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 the exact usage context: one-off, stateless page interaction. It closes with an explicit routing condition: 'For multi-step interaction on a shared page use session_click instead,' which tells the agent when to prefer the sibling.

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