Move an item to a folder

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

Beyond the annotations, it discloses a real side effect — the placement is recorded as a human choice so automatic classification will not re-move the item — and states failure conditions when item or folder is missing. The no-op case when moving to the current folder usefully reinforces the idempotentHint rather than contradicting it.

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 short sentences, each carrying distinct information: purpose, side effect, no-op case, and failure mode. The scenario example is front-loaded so an agent can decide quickly.

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 two-parameter mutation with annotations and no output schema, the description covers the important unknowns: persistence of the move, idempotency, and error conditions. It does not describe what the call returns on success, which is the only notable gap.

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 100%, and the schema already tells the agent that `folder` is a target folder id from driftnet_folders and `id` is the item to move. The description adds only the framing of a "reader's folder" and no syntax or format detail beyond the schema, so baseline 3 applies.

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 states a concrete verb and resource ("File an item into one of the reader's folders") and anchors it with a realistic scenario ("when it was sorted into the wrong one"). It distinguishes moving from automatic classification, though it never names a specific sibling such as driftnet_save or driftnet_enrich to contrast against.

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?

It gives a clear trigger condition (correcting a mis-sorted item) and rules out concern about re-classification. It stops short of explicit when-not guidance or naming which sibling to use for adjacent tasks like saving a new item.

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