qt_mouse_dbl_click

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'direct delivery', which vaguely implies a synthetic event, but does not mention side effects, prerequisites, cursor movement, or return behavior. This is insufficient for a tool that triggers a UI action.

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 concise and front-loaded with the primary action. The second sentence efficiently explains coordinate behavior. No filler or redundant content, but it could have used the brevity to include more safety or behavioral context.

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 tool has no annotations and a non-trivial parameter surface (6 params), the description is incomplete. It lacks context about session requirements, whether physical cursor movement occurs, and how button/modifiers interact with the double-click. The output schema existence does not compensate for these gaps.

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 description explains the x/y parameters in useful detail (relative coordinates, optional, center default), which adds value beyond the schema. However, it says nothing about 'button' (even though it has a default of 'left' and possible variants) or 'modifiers', and schema description coverage is 0%. These parameters remain semantically unclear.

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: 'Send a double-click to a UI element'. This uses a specific verb and resource, and distinguishes the tool from single-click or other mouse tools. The 'direct delivery' note adds a mode distinction.

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 provides explicit guidance on x/y coordinate semantics (optional, relative to element top-left, both or neither, omitted means center). However, it does not explicitly state when to use this tool over alternatives like qt_mouse_click or qt_mouse_press; usage context is only implied by the tool name.

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