dblclick

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

No annotations are provided, so the description carries the full burden and mostly doesn't. It doesn't disclose whether the element is auto-scrolled into view, what happens if the target is missing or obscured, or whether the action waits for completion.

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?

A single front-loaded sentence that names the action and the accepted targeting forms with zero filler. Nothing is padded or restated.

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 an action tool with no annotations and no output schema, the description is thin: it omits the meaning of tabId, the element-readiness/auto-scroll behavior, and failure modes. It gives just enough to attempt a call but not enough to call it reliably.

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 0%, and the description does partially compensate by clarifying that 'target' accepts either a ref or a CSS selector, which is real information beyond the bare string type. However, 'tabId' remains completely undefined in both the schema and the description, so the compensation is incomplete.

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 (double-click) and resource (element), which cleanly separates it from the sibling 'click' by action semantics. It stops short of any sibling routing or scope detail, but the core action is unambiguous.

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?

Usage is only implied by the verb itself; the description never says when a double-click is preferred over click, hover, or drag, nor whether the element must be visible or in the viewport first. An agent can infer intent but gets no explicit conditions.

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