wavexis_check

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

Description states toggling behavior which contradicts annotations idempotentHint=true (toggling is not idempotent). Per guidelines, score 1 for description contradicting annotations.

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?

Four focused sentences: purpose, alternatives, side effects, return format. No redundancy, front-loaded with key 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 output schema and annotations, description covers purpose, side effects, return values. Missing explanation of idempotency discrepancy, but otherwise complete for a simple tool.

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?

Description adds context that selector targets checkbox/radio, but does not elaborate on session_id or format beyond schema. Schema descriptions are minimal, so baseline is 3.

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 'Check a checkbox or radio button matching a CSS selector' and explicitly distinguishes from siblings wavexis_uncheck and wavexis_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?

Provides explicit guidance: 'Use wavexis_uncheck to uncheck a checkbox or wavexis_click for generic element activation', defining when to use this tool vs alternatives.

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