delete_files

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

No annotations provided, so description carries full burden. Thoroughly explains deletion rules (KB files unlinked, reference files de-indexed), non-idempotent nature, partial success, per-ID error isolation, no external auth/rate limits, and return format. Comprehensive.

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?

Description is well-structured with key point first. Every sentence adds value, though slightly verbose. Could be tightened without losing meaning, but effective overall.

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 single parameter, no output schema, and no annotations, the description adequately covers behavior, return format, usage context, and edge cases (partial success, unknown IDs). Complete for the tool's complexity.

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?

Only one parameter ('ids') with schema coverage 100%. Description adds value by specifying batch size limit (max 500) and that per-ID failures are isolated. Baseline 3, so +1 for additional context.

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 it is a destructive batch delete for up to 500 files by ID. Distinguishes from 'delete_file' by noting same deletion rules but batch operation. Meets specific verb+resource criteria.

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 suggests previewing with 'list_files' to confirm IDs before deleting. Explains behavior with unknown IDs and partial success, providing clear guidance on when to use and what to expect. Lacks explicit 'do not use when' conditions, but context is sufficient.

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