wavexis_dom_remove_attr

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

Beyond annotations (destructiveHint=true), description explicitly states 'Mutates the DOM by deleting the attribute' and specifies return format ('JSON string with keys: status'). Adds value by detailing the exact mutation and response structure.

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, alternative usage, and side effects/return. Key information is front-loaded with zero wasted 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?

For a simple attribute removal tool, description covers purpose, alternative, side effects, and return. Output schema exists and annotations provide safety hints. Could mention idempotency or error handling, but overall sufficient.

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 has 0% description coverage, but parameter names are self-explanatory (name, selector, session_id) and schema provides types and minLength. The tool description does not add extra parameter details, leaving schema as the sole source. Adequate but not enhanced.

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?

Clearly states the action ('remove an attribute') and the target ('element matching a CSS selector'). Explicitly distinguishes from sibling wavexis_dom_set_attr, providing a precise purpose.

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?

Mentions when to use the alternative tool (wavexis_dom_set_attr) for restoring or changing attributes, giving clear guidance. Could additionally note prerequisites like having a valid session, but schema covers required parameters.

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