Batch Permanently Delete Items

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

Discloses critical behavioral traits: deletion is irreversible, only touches already-soft-deleted items, cascades to child rows, and returns a confirmation summary. No annotations exist, so description fully covers safety and side effects.

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 a single well-structured paragraph with clear sentences. It is concise yet comprehensive, covering all necessary information without redundancy.

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 7 parameters and no output schema, the description is complete: it covers the purpose, filtering options, confirmation workflow, safety constraints, and alternative tools. No gaps are evident.

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. The description adds significant value by explaining the purpose of each filter (e.g., older_than_days) and the two-phase confirmation process for the resolution parameter. It clarifies that items list or filters must be provided but not both.

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 tool's function: 'Permanently and irreversibly delete many soft-deleted items at once (batch purge from the trash).' It distinguishes from the singular 'purge_item' and references 'restore_items' as an alternative for recovery.

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 describes when to use the tool (for batch deletion of already soft-deleted items) and when not to (use restore_items for recovery). Provides detailed workflow: first call returns a confirmation conflict, then user must explicitly agree before passing 'confirm' as resolution.

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