wavexis_shadow_click

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

The description adds that it pierces shadow boundaries, a key behavior beyond annotations. Annotations indicate destructiveHint=true, and the description confirms it's a click action. No contradictions.

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 short and direct, with no wasted words. It uses a docstring format with sections for Args and Returns, which is well-structured. A bit more detail on parameters would improve it.

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 click tool with an output schema, the description is sufficiently complete: it specifies the action, target (shadow DOM), and simple return. It covers the essential context for selecting this tool over siblings.

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% (per context), meaning the description should compensate. However, the description only says 'Shadow click parameters (selectors)' without explaining the selectors array or session_id. It adds minimal value beyond the schema's brief descriptions.

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 tool clicks an element inside a shadow DOM tree, using a selector chain to pierce boundaries. This distinguishes it from siblings like wavexis_click (regular click) and wavexis_iframe_click (iframe 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 implies usage for shadow DOM elements but provides no explicit when-to-use, when-not-to-use, or alternative tools. It lacks guidance on conditions for use.

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