superset_create_dashboard

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

With no annotations provided, the description carries the full burden. It discloses that the dashboard is initially empty and that the response includes the id, which is useful. However, it omits other behavioral aspects such as permission requirements, effects of 'published'/'slug', and any side effects.

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 concise: two sentences, no filler, and directly states the purpose and return. It is front-loaded with the core action and outcome.

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?

The description covers the essential purpose and return value, and an output schema exists for return structure. However, it lacks parameter semantics and workflow context (e.g., what 'empty' means, relationship to add/chart tools), leaving gaps for a creation tool with no annotations.

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 input schema has 0% description coverage, and the tool description does not explain any of the parameters (dashboard_title, published, slug). The schema only provides types and defaults, so there is no added meaning from the description to guide parameter usage.

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 action ('Create'), the resource ('dashboard'), and key characteristics ('empty', 'Returns the new dashboard with id'). This differentiates it from sibling tools like update, delete, list, and get dashboards.

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 provides clear use context: creating a new empty dashboard. It also hints at the next steps ('Then add charts and filters'), implying a workflow. However, it does not explicitly mention when not to use this tool or direct users to alternative tools for modifications.

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