create_dashboard

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

No annotations provided; description explains dry_run behavior ('validate inputs and return a preview without making any changes') and parameter defaults, offering sufficient transparency for a creation tool.

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?

Concise 6-line description with clear Args section. Front-loaded with main purpose. Slightly longer than minimal but each sentence adds value.

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?

Covers creation and post-creation guidance; output schema exists so return values need not be described. Missing edge-case details but adequate for primary use cases.

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%, but description adds meaningful explanations for all three parameters (dashboard_title, published, dry_run) beyond type/default, including dry_run's validation purpose.

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 'Create a new, empty dashboard' and provides follow-up actions (create_chart, update_dashboard), distinguishing it from sibling tools like create_chart and update_dashboard.

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?

Explicitly advises using create_chart or update_dashboard after creation, giving clear context for subsequent steps. Does not include when-not-to-use scenarios but adequately guides usage.

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