Undo a batch move

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

Discloses behavior beyond the annotations: single-use semantics ("a second call with the same id fails, so don't retry blindly"), 24-hour validity, a 20-batch window, and the full set of failure conditions including a deleted target folder. This is consistent with idempotentHint=false and adds real operational context.

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?

Front-loaded with the effect, then usage, then id semantics and failure modes. Every sentence carries distinct information; nothing is redundant.

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?

An output schema exists, so return values need not be explained. Given a single-parameter mutation tool, the description covers trigger conditions, lifetime limits, idempotency, and failure modes completely.

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 coverage is 100%, so the baseline is 3, but the description goes further by explaining where the id comes from, that it must be passed exactly as returned, and that it expires after 24 hours or falls outside the 20 most recent batches. The validity constraints are meaningful additions not present in the schema.

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?

States a specific verb and resource (revert a driftnet_move_items batch) and describes the exact effect: items return to their origin folder, and unfiled items return to automatic sorting. This distinguishes it clearly from driftnet_move_items and the other siblings.

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?

Explicitly says when to use it ("right after a move the reader rejects") and names the alternative for a different intent ("to put items somewhere else instead, call driftnet_move_items again"). Both the trigger and the alternative are spelled out.

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