browser_hover

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

Annotations already indicate the tool is open-world and non-destructive. The description adds value by clarifying that it only hovers (no click), which is a key behavioral trait not fully captured by annotations.

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 extremely concise with two sentences. The first sentence front-loads the action and purpose, the second provides a critical clarification. No wasted words.

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 simplicity of the tool (one parameter, no output schema, no nested objects), the description covers all essential aspects: what it does, when to use, and distinguishing guidance. It is complete for effective agent usage.

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%, and the schema itself describes the parameter adequately ('CSS selector of the element to hover over'). The tool description does not add additional parameter-level information beyond what the schema provides, resulting in a baseline score of 3.

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 action ('hover the pointer') and the resource ('an element') with a specific purpose ('to trigger hover menus/tooltips'). It also explicitly distinguishes from the sibling tool 'browser_click' by stating it does not 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?

The description explicitly says when to use (to trigger hover menus/tooltips) and when not to use ('Does not click'), and provides the alternative tool ('use browser_click for that').

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