trash

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

With no annotations, the description carries the behavioral burden and does disclose the key trait: it moves to a trash folder and never hard-deletes. It does not mention permissions, side effects, or what happens if the trash folder is missing, but the presence of an output schema reduces the need to explain returns.

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?

A single, front-loaded sentence with zero waste. Every clause earns its place by stating the action, destination, and non-destructive guarantee.

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 tool with an output schema, the description is mostly complete, but it omits how to specify the required 'item' parameter. That gap is significant enough to limit the score, though not fatal given the tool's simplicity.

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 0%, and the description adds some meaning by specifying that 'item' can be a link or folder. However, it does not explain how to identify that item (ID, path, title), so the compensation is only partial.

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 ('Move') and resource ('a link or folder') with the exact destination ('Other bookmarks > _Trash'). This distinguishes it from the generic sibling 'move' tool and makes the tool's purpose unmistakable.

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 parenthetical 'never hard-deletes' clarifies when to use this tool: for reversible removal instead of permanent deletion. However, it does not explicitly name alternatives (e.g., 'move' or a hypothetical 'delete') or state when not to use it.

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