wavexis_double_click

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

Annotations already indicate destructiveHint=true and openWorldHint=true. The description adds concrete side effects ('Fires two rapid click events... may open files, edit cells') and return format, enhancing transparency. However, it does not mention session or browser state implications.

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?

Every sentence adds value: purpose, alternatives, side effects, and return format. Front-loaded with the core action. No unnecessary 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 tool's complexity and that output schema exists, the description covers purpose, usage guidance, side effects, and return structure. It lacks mention of session management but overall is adequate for selection.

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 descriptions for all parameters (100% coverage), so baseline is 3. The tool description adds no additional meaning beyond what the schema already provides, so it meets baseline without adding extra value.

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 'Double-click an element matching a CSS selector', using a specific verb and resource. It clearly distinguishes itself from siblings by explicitly mentioning alternatives (wavexis_click for single clicks, wavexis_nl_click for natural language).

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?

Provides explicit context on when to use alternatives and describes side effects. However, it does not explicitly state when not to use this tool or mention prerequisites (e.g., needing a session), leaving minor gaps.

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