Batch Restore Items

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

Discloses reversibility ('Restores are reversible - you can delete the items again'), direct execution ('executes directly'), and return type ('returns a summary'). No annotations, so description carries full burden. Could mention permissions or side effects, but sufficient for safe use.

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 covering purpose, parameter usage, and behavioral notes. No wasted words. Each sentence serves a distinct role. Front-loaded with purpose.

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?

Given 5 params, no annotations, no output schema, description covers all needed: how to call (items vs filters), behavior (reversible, direct), and what to expect (summary). Satisfies information needs for a batch restore tool.

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 100% so baseline 3. Description adds value by clarifying mutual exclusivity of items and filters, grouping filter options, and noting default for days. Helps agent understand parameter relationships beyond schema.

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?

Clear verb 'restore' with resource 'soft-deleted items' and scope 'batch'. Title 'Batch Restore Items' reinforces. Distinguishes from sibling 'restore_item' (singular) and 'purge_items' (permanent delete).

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: batch restore via items list or filters. Provides alternative: 'Use purge_items to permanently delete instead.' Covers both when-to and when-not.

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