Create a new (empty) dashboard

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

Description mentions the return value (new id) and that the dashboard is initially empty, but does not disclose behavioral details such as whether layout parameter is supported (it exists in schema but is not mentioned), potential name conflicts, or permission requirements. No annotations are provided to compensate.

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?

Two sentences, front-loaded with main action, and efficiently includes usage alternatives and next steps without extraneous text.

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?

For a tool with 3 parameters (one nested), no output schema, and no annotations, the description covers the primary use case and return value but omits explanation of the layout parameter, which is a gap in completeness.

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 has 3 parameters with only 33% description coverage. The tool description adds meaning for 'name' and 'description' (optional), but fails to mention the 'layout' parameter, which is a nested object with no schema description. This omission leaves the agent uninformed about a significant parameter.

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?

Title and description clearly state the tool creates an empty dashboard with name and optional description, returning the new id. This distinguishes it from sibling tools like dashboard_template_get.

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?

Description explicitly explains when to use this tool (to create an empty dashboard) and provides alternatives: using dashboard_template_list and dashboard_template_get for pre-populated templates, and widget_create to add widgets afterward.

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