wavexis_iframe_click

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

Annotations only indicate destructiveHint=true and readOnlyHint=false. The description adds specific side effects: 'Triggers click handlers and may navigate or mutate the iframe DOM' and describes return format, going well beyond annotations. No contradiction.

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?

Three concise sentences: purpose, usage guidance, side effects and return. No fluff, well-structured and front-loaded with the action.

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?

With a simple click action, annotations present, and output schema defined, the description covers purpose, when-not-to-use, side effects, and return format. Complete for effective tool selection and invocation.

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 tool description does not discuss parameters, but the input schema provides descriptions for all three properties ('CSS selector inside the iframe', etc.), resulting in high schema description coverage. Thus baseline 3 is appropriate; the description adds no extra semantic 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 clearly states 'Click an element inside an iframe' with a specific verb and resource. This distinguishes it from sibling tools like wavexis_click (click in main frame) and wavexis_iframe_fill (fill inside iframe).

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 advises to use wavexis_iframe_eval only when actions cannot be expressed by click/fill, providing a clear when-not-to-use. It does not exhaustively list all alternatives but gives effective guidance.

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