Browser Hover

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

With no annotations provided, the description must carry the full burden. It only mentions a side effect (reveals menus/tooltips) but fails to disclose other behaviors such as whether it waits for elements, how errors are handled, or if it triggers JavaScript events. No mention of potential requirements (e.g., element must be visible).

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 very short, which is good for conciseness, but it lacks critical information. It is front-loaded with the verb and resource, but the brevity undermines usefulness. It is not padded, but it does not earn its place by adding value beyond what the name implies.

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 tool with 3 parameters and no annotations, the description is inadequate. It does not explain return values despite having an output schema, nor does it specify parameter semantics. The sibling tools are numerous, so more context is needed to select correctly.

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 0%, so the description must compensate for all parameters. It only explains 'ref' implicitly (hover by ref) but gives no details on 'tab' or 'session'. With 3 parameters and zero coverage, this is a critical gap.

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 a specific verb and resource ('hover over an element by ref') and notes a common effect (reveals menus/tooltips). However, it does not distinguish from sibling actions like browser_click or browser_find, and the purpose is somewhat generic. It is clear enough but lacks differentiation.

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 gives no guidance on when to use this tool vs alternatives. It does not mention that hovering is needed for dynamic UI elements, nor does it exclude cases where click would suffice. No references to related tools like browser_click or browser_find.

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