directus_update_dashboard

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Update' implies mutation, the description fails to specify if the operation is idempotent, what happens to existing dashboard panels or permissions, whether it requires admin privileges, or what the return value contains.

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?

While brief, the description is inappropriately sized given the lack of schema documentation. The '[UNIFIED]' tag wastes valuable leading characters that should establish context. For a tool requiring three parameters with nested objects, a single fragment sentence is insufficient.

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 inadequate for a mutation tool handling complex nested data. With no output schema, no annotations, and zero schema coverage, the description should explain the operation's scope, side effects, and parameters. Instead, it provides only a tautological fragment.

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?

With 0% schema description coverage, the description completely fails to compensate. It provides no explanation of the 'site' parameter (is this a URL, slug, or ID?), what the 'id' refers to (dashboard ID vs. site ID), or what structure is expected in the nested 'data' object (fields, types, required values).

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 states the basic action (Update) and resource (dashboard settings), distinguishing it from sibling tools like directus_create_dashboard or directus_delete_dashboard. However, the '[UNIFIED]' prefix is noise that adds no semantic value, and 'settings' is ambiguous—it's unclear if this modifies the dashboard entity itself or only a subset of configuration properties.

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?

No guidance provided on when to use this versus alternatives (e.g., directus_create_dashboard for new dashboards), prerequisites (e.g., needing an existing dashboard ID), or whether this supports partial vs. full updates. The agent receives no decision-making context.

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