update_dashboard

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds meaningful context about a confirmation gate ('confirm=true is required') and preview-versus-update behavior. However, it does not describe side effects, return values, or what a preview actually returns, leaving important behavioral gaps.

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, front-loaded sentence that conveys the key purpose and the critical confirm requirement. Every word adds value, with no filler or redundancy.

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 5 parameters, no output schema, no annotations, and a complex pre-view/update operation, the description is too sparse. It omits return value behavior, side effects, permissions, and how to interact with preview mode. The sibling list suggests related tools but the description does not connect to them.

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 description coverage is 0%, so the description must compensate for the 5 parameters. It names 'layout/metadata/publication' which maps loosely to position, metadata, and published, but does not explain their structure or the roles of dashboard_id and confirm beyond 'confirm=true is required'. This is minimal added value over the 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?

The description clearly identifies the tool as updating dashboard layout, metadata, and publication status, which distinguishes it from sibling tools like create_dashboard or get_dashboard. The phrase 'Preview or update' adds some ambiguity about the exact dual behavior, but the core purpose is clear.

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 implies usage by stating 'Preview or update' and explicitly requires 'confirm=true' for actual updates, which is a practical usage guideline. However, it does not explicitly contrast with alternatives like create_dashboard or add_chart_to_dashboard, nor does it explain when to choose preview mode.

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