directus_delete_file

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

Discloses the critical behavioral trait of being irreversible ('This action is irreversible'), which is essential since no annotations exist. However, lacks other important behavioral context: error handling when file doesn't exist, cascading effects on references to this file, or permission requirements.

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?

Extremely concise with two sentences. The '[UNIFIED]' prefix appears to be metadata noise that doesn't aid tool selection. Otherwise zero waste—immediately states purpose and irreversibility.

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?

Inadequate for a destructive operation with zero annotations. Missing parameter documentation (critical given 0% schema coverage), no output specification, and no distinction from bulk deletion sibling. The irreversibility warning is the only complete behavioral disclosure.

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 for both 'site' and 'id' parameters. Description fails to compensate by explaining what constitutes a valid site identifier or file ID format, or whether 'id' refers to the Directus file ID specifically.

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?

States specific verb ('Delete') and resource ('file') clearly. However, fails to distinguish from sibling tool 'directus_delete_files' (plural), leaving ambiguity about whether this is single-file vs bulk deletion.

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?

Provides no guidance on when to use this versus the plural variant 'directus_delete_files', nor prerequisites like requiring the file to exist or permission requirements. Only contains the irreversibility warning.

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