directus_delete_collection

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

No annotations provided, so description carries full disclosure burden. While it states irreversibility, it omits crucial behavioral details: cascading effects on relations, whether associated fields/dashboards are affected, or authentication requirements for destructive schema changes.

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 logical flow (action followed by warning). However, the '[UNIFIED]' prefix wastes space without clarifying meaning for the agent. Otherwise efficiently structured.

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?

Insufficient for a destructive operation with 2 undocumented parameters and no output schema. The irreversibility warning addresses one gap, but missing: parameter explanations, cascade behavior, return value structure, and error conditions.

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 description coverage is 0% (neither 'site' nor 'collection' have descriptions). Description completely fails to compensate by explaining what 'site' refers to (instance identifier? project name?) or the expected format for 'collection'.

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?

Clear verb-resource pair ('Delete a collection') with explicit scope ('and all its data'). Distinguishes from item-level deletion (directus_delete_items) by clarifying it removes the schema structure plus data. The '[UNIFIED]' prefix is extraneous noise but doesn't obscure the core 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?

Provides critical safety guidance that the action is 'irreversible,' which informs when to use (only when certain). However, lacks explicit alternatives (e.g., distinguishing from directus_delete_items) or prerequisites like permissions required.

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