delete_files

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

Discloses destructive nature, physical-deletion rules per file type, isolation of per-ID failures, non-idempotency, no external auth/rate limits, and return structure. No annotations to rely on, so description carries full burden and does so thoroughly.

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?

Four sentences, each earning its place. Front-loaded with key info. No 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 no annotations and no output schema, description covers behavior, edge cases, idempotency, auth, rate limits, return value, and preview alternative. Highly complete for a batch delete 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 is 100% with clear description for `ids` parameter. Description adds context about batch behavior and max 500, though max already in schema. Extra value justifies above baseline.

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?

Clearly states 'DESTRUCTIVE batch — delete up to 500 files by ID in one call' with verb (delete), resource (files), and batch scope. Distinguishes from sibling `delete_file` by referencing same deletion rules.

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?

Specifies when to use: batch delete of up to 500 files. Provides alternative: 'To preview the set before deleting, run `list_files` with the same filter and confirm the IDs.' Could explicitly state when not to use, but clear enough.

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