Restore Item

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

Discloses that only soft-deleted items can be restored, not hard-deleted. Mentions return value 'restored item summary with normal redaction rules'. Annotations already indicate not read-only and not destructive; description adds relevant behavioral details without contradiction.

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 with no wasted words. Front-loaded with the core action, followed by usage guidance, then return value. Every sentence adds value.

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 one parameter and no output schema, the description covers purpose, usage conditions, and return format. Minor omission of error handling or id validation, but overall complete enough.

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?

The single parameter 'id' is fully described in the schema with 100% coverage. The description mentions 'by id' but adds no additional semantic meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the verb 'restore' and the resource 'soft-deleted vault item from trash by id'. It distinguishes from sibling tools like delete_item by specifying it is the inverse operation for soft-deleted items.

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 states when to use: 'after delete_item or delete_items when permanent was omitted or false'. Also specifies when not to use: 'hard-deleted items cannot be restored'. Provides clear context for selection.

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