wavexis_drop

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

Annotations indicate destructiveHint=true, which the description aligns with. Beyond annotations, it details side effects (dispatches dragEnter, dragOver, drop events) and return format, adding useful context. 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 well-structured: purpose first, then alternatives, side effects, return. It is informative but slightly long; could be trimmed without losing value.

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 tool's complexity (many parameters, side effects), the description covers purpose, alternatives, behavior, and return format. With an output schema present, it is sufficiently complete.

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 description does not elaborate on individual parameters; the schema (with 0% coverage from the description) already has detailed descriptions for each property. The description adds no extra parameter guidance, so a baseline 3 is appropriate.

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 it drops files or MIME-typed data onto an element via drag events. It explicitly distinguishes from sibling tools wavexis_set_files (for file inputs) and wavexis_drag (for dragging DOM elements).

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 provides explicit guidance: 'Use wavexis_set_files for standard <input type="file"> uploads or wavexis_drag for dragging an existing DOM element to another element.' This clearly indicates when to use alternatives.

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