update_dashboard

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

Absent annotations, the description must disclose behavioral traits. It only states 'Update', which implies mutation, but does not specify required permissions, side effects, idempotency, or whether changes are reversible. This lack of transparency hinders correct usage.

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 a single sentence with no wasted words, achieving brevity. However, it is overly terse and lacks structure (e.g., bullet points or sections). It could be expanded without losing conciseness.

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?

Given the complexity (multiple optional fields, collection_id with null option) and lack of annotations or output schema, the description is insufficiently complete. It omits behavior details, parameter guidance, and return information, leaving significant gaps for correct invocation.

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 description adds no parameter information beyond what the input schema already provides (schema description coverage is 0%). The schema itself has descriptions for id, name, description, and collection_id, but the description does not enhance or contextualize these. With low coverage, the description should compensate but fails.

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 verb 'Update' and the resource 'existing dashboard in Metabase', making the purpose unambiguous. It distinguishes from sibling tools like create_dashboard or copy_dashboard, but lacks specificity about which attributes can be updated, preventing a higher score.

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 is given on when to use this tool versus alternatives such as create_dashboard or save_dashboard. The description does not mention prerequisites, context, or exclusions, leaving the agent without decision support.

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