directus_create_dashboard

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

With no annotations provided, the description carries the full burden but only implies mutation via the word 'Create'. It fails to disclose idempotency behavior, return value structure, auth requirements, or side effects. No contradictions with annotations (none exist).

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 brief (one sentence), but the '[UNIFIED]' tag wastes space without aiding tool selection. Front-loaded with metadata noise rather than actionable guidance.

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 5-parameter mutation tool with no output schema and zero schema documentation. Missing critical context: parameter semantics, return structure, error handling, and relationship to other dashboard/panel tools.

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 (no field descriptions), and the description adds zero semantic value for any of the 5 parameters (site, name, icon, note, color). Does not explain what 'site' refers to (ID vs name), valid icon values, or color format.

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 'Create' (verb) and 'insights dashboard' (resource) clearly enough, but lacks differentiation from sibling tools like directus_create_panel or openpanel_create_dashboard. The '[UNIFIED]' prefix adds noise without clarifying 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 no guidance on when to use this versus directus_update_dashboard, directus_create_panel, or prerequisites such as required permissions or site existence. No mention of error conditions like duplicate names.

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