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

The description says the tool moves a folder and its files to trash, which is a destructive/state-changing operation, yet the annotations declare destructiveHint=false. This is an annotation contradiction and misleads the agent about the tool's safety profile.

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 one concise, front-loaded sentence that conveys the core action and scope without wasted words.

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 single-parameter tool this is very brief, but it omits essential context: what the caller should pass as reference, what happens to the trashed items or whether this is recoverable, and any return/confirmation behavior. The contradictory destructiveHint annotation further undermines completeness.

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%, so the description must compensate for the undocumented 'reference' parameter. It only implies that reference identifies the folder to be removed, but does not explain the reference format, required scope, or how it is used.

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 uses a specific verb ('Move') and clearly identifies the resource ('a folder and its files') and result ('to trash'). It is distinct from sibling folder operations like create, get, list, and rename.

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?

There is no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites mentioned. The description only states the action, leaving the agent to infer suitability from the tool name.

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