Permanently delete specific recycle bin items

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

Annotations already declare destructiveHint=true, but the description adds critical context the annotations cannot: irreversibility, the confirm=true guard that refuses otherwise, and the exact return shape {purged, failed}. Minor gap: no mention of auth requirements or partial-failure semantics.

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-loads the irreversible warning, then the sibling preference, then the required workflow, then the guard, then the return shape. Every sentence earns its place with no repetition.

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?

Covers purpose, irreversibility, sibling differentiation, prerequisite listing call, confirmation guard, and return shape. With annotations covering destructiveness and a 100% schema, nothing an agent needs to call this safely is missing.

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 baseline is 3, but the description adds meaning beyond schema: the confirm gate is tied to the refusal behavior, and paths are framed as 'in-bin paths from zspace_recycle_list' which clarifies the required format source. It also explains the consequence of omitting confirm.

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 (permanently delete) and resource (named items in the personal recycle bin) with scope precision ('only the named items, leaving everything else untouched'). This clearly distinguishes it from zspace_recycle_empty and zspace_remove.

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 routes the agent: 'Prefer this over zspace_recycle_empty whenever the goal is to free the space held by specific files.' Also prescribes calling zspace_recycle_list first and showing the user the destruction set, which is a complete when-to-use workflow.

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