directus_delete_version

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Delete' implies a destructive mutation but the description fails to confirm if deletion is permanent, reversible, or if it triggers cascading effects. No disclosure of auth requirements or rate limits.

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?

The description is brief (effectively one sentence plus metadata), but the '[UNIFIED]' prefix is noise that doesn't help an AI agent understand the tool's function. Otherwise free of fluff, though severe under-specification limits its usefulness.

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?

Severely incomplete for a destructive operation with 0% parameter documentation and no output schema. The description fails to explain what gets returned upon success, error conditions, or the specific nature of the 'version' resource being deleted.

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% for both 'site' and 'id' parameters. The description provides no hints about the format of 'site' (URL, subdomain, or instance name?) or that 'id' refers to the version identifier, leaving parameters effectively undocumented despite the tool name providing minimal 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?

States a specific verb ('Delete') and resource ('version'), distinguishing it from siblings like directus_create_version, directus_get_version, and directus_update_version. However, it omits that this is a Directus content version and includes the metadata tag '[UNIFIED]' which doesn't aid clarity.

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 tool versus alternatives like directus_promote_version or directus_update_version. No mention of prerequisites (e.g., permission requirements) or irreversibility warnings for the deletion operation.

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