directus_get_dashboard

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

No annotations are provided, so the description carries full disclosure burden. It implies read-only behavior via 'Get' but does not confirm safety, idempotency, error responses (e.g., 404 for missing ID), or authentication requirements expected for Directus dashboard access.

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?

Single sentence is appropriately brief, but the '[UNIFIED]' prefix at the beginning wastes space with an unexplained internal tag. Information is front-loaded after the tag, though the tag disrupts immediate comprehension.

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?

Lacks output schema and annotations. For a retrieval tool with zero schema documentation, the description should explain what dashboard details are returned, potential error states, and parameter specifics. It provides only the minimal operation identification.

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 coverage is 0% for both parameters. The description mentions 'by ID' addressing the 'id' parameter conceptually, but provides no information about the 'site' parameter (e.g., whether it represents a Directus instance, project name, or URL). No format constraints, examples, or validation rules are provided to compensate for the empty schema.

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 clear verb ('Get') and resource ('dashboard details') with scope ('by ID'). However, it does not explicitly distinguish from sibling tool 'directus_list_dashboards' (which retrieves multiple dashboards). The '[UNIFIED]' prefix adds noise without semantic value.

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?

Contains no explicit guidance on when to use this tool versus alternatives like directus_list_dashboards. While 'by ID' implies use when a specific dashboard identifier is known, there are no stated prerequisites, error conditions (e.g., invalid ID), or workflow guidance.

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