directus_delete_dashboard

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context about the cascade behavior (panels are deleted with the dashboard), but fails to disclose other critical mutation traits such as irreversibility, required permissions, or side effects beyond the cascade.

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 and front-loaded, but the '[UNIFIED]' tag appears to be metadata leakage rather than useful content. Given the complete absence of schema descriptions and annotations, the description is underspecified rather than appropriately concise.

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?

For a destructive operation with zero schema description coverage and no annotations, the description is incomplete. It lacks parameter documentation, safety warnings, and return value information (though no output schema exists). The cascade mention is the only saving grace.

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?

The input schema has 0% description coverage for both 'site' and 'id' parameters. The description adds no compensatory information about what these parameters represent (e.g., that 'site' refers to the Directus instance identifier and 'id' refers to the dashboard UUID), leaving them completely undocumented.

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?

The description clearly states the specific action ('Delete') and resource ('dashboard'). It effectively distinguishes from the sibling tool 'directus_delete_panel' by explicitly noting that this operation also deletes 'its panels', indicating cascading behavior.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like 'directus_delete_panel' or 'directus_update_dashboard'. While the cascade behavior ('and its panels') implies this is for complete removal, there are no stated prerequisites, conditions, or warnings about irreversibility.

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