wavexis_dom_remove

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description confirms removal but adds no extra behavioral context (e.g., permanence, effect on associated data). It is adequate but not enhanced.

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 concise (two sentences) but lacks structure; it could benefit from a brief note on parameter usage or return value. It is not verbose but also not optimally organized.

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 simple tool, the description misses details like the format of the selector (CSS syntax) or session_id. An output schema exists but the description could briefly mention the return format. Overall incomplete for effective tool use.

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 description coverage is 0%, yet the description only mentions 'input: Element removal parameters' without explaining what 'selector' and 'session_id' are or how to use them. This fails to compensate for the lack of schema 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 action 'Remove an element matching a CSS selector from the DOM', using a specific verb and resource, and distinguishing it from sibling DOM tools like wavexis_dom_focus or wavexis_dom_get.

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 gives no guidance on when or when not to use this tool compared to other DOM manipulation tools like wavexis_dom_remove_attr or wavexis_dom_set_attr. An agent cannot determine appropriate usage context from this alone.

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