browser_click_mark

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states 'Click an element' without addressing side effects like navigation, failure behavior if no snapshot exists, or what the response contains. The snapshot dependency is noted, but other behavioral traits remain opaque.

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 a single, clear sentence with no unnecessary words. It is front-loaded with the action and target, making it easy to parse quickly.

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 one-parameter tool, the description still lacks essential context: what Set-of-Marks means, where marks come from, what prerequisites must hold, and what outcome to expect. The existence of an output schema does not compensate for the absence of these operational details.

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 input schema has 0% description coverage and the description never mentions mark_id, how to obtain it, or its relationship to the Set-of-Marks snapshot. The description fails to add any meaning beyond the bare schema definition of an integer parameter.

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 uses a specific verb ('Click') and resource ('element from latest Set-of-Marks snapshot'), clearly distinguishing it from navigation, scrolling, and generic action tools. The mention of 'Set-of-Marks' adds specificity beyond what the name alone implies.

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 phrase 'from the latest Set-of-Marks snapshot' implies a clear prerequisite (a snapshot must exist) and contextual usage, but it does not explicitly name alternatives like browser_act or state when not to use this tool. This provides clear context without exclusions.

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