directus_delete_files

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

No annotations provided, so description carries full burden. It successfully adds critical behavioral context: 'This action is irreversible.' However, lacks details on error handling (e.g., partial failures), validation, or required permissions.

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?

Two sentences with minimal waste. '[UNIFIED]' tag is metadata cruft, but otherwise efficient and front-loaded with the action verb.

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?

With 0% schema coverage, no annotations, and no output schema, the description fails to document the 'site' parameter at all. Only redeeming quality is the irreversibility warning for this destructive operation.

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 has 0% description coverage. Description mentions 'multiple files' implying the ids parameter purpose, but provides no semantics for the 'site' parameter (URL? Name? ID?) or expected ID format in the array.

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 'Delete multiple files' with specific verb and resource. The word 'multiple' effectively distinguishes from sibling tool directus_delete_file. The '[UNIFIED]' prefix is unnecessary metadata noise but doesn't obscure the purpose.

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?

Implies bulk usage via 'multiple files' but does not explicitly contrast with directus_delete_file (singular) or state when to prefer one over the other. No guidance on prerequisites or permissions needed.

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