Restore files from the recycle bin

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

Annotations only carry openWorldHint, so the description must disclose the mutation profile and does: it clarifies the operation restores data rather than deleting it, and states a hard precondition (bin must not be emptied). It does not cover permissions required or behavior when a destination path already exists, leaving a modest gap for a mutation tool.

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?

Three sentences, purpose front-loaded, followed by the critical path constraint and then recovery context. No redundant restatement of the name or schema; every sentence carries information.

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 the brief 'Returns {restored, failed}' is supplementary rather than required. For a mutation tool with near-empty annotations, it discloses the non-destructive nature and precondition but omits auth requirements and destination-overwrite behavior.

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 real semantic value beyond the schema's example: paths must be in-bin paths from zspace_recycle_list, not original locations. That constraint is the main way an agent would get this wrong, and the description prevents it.

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 (restore) and resource (items from the personal recycle bin to their original locations). Easily distinguished from sibling recycle tools (list, purge, empty) whose names imply different operations.

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 frames this as the recovery path after an accidental zspace_remove, names the precondition ('only works while the bin has not been emptied'), and points to zspace_recycle_list as the source of valid paths. When-to-use, when-not-to-use, and the related sibling are all covered.

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