superset_dashboard_create

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

No annotations are provided, so the description carries the full burden. It discloses a critical side effect: specifying roles automatically syncs datasource_access to all dashboard datasets. It also notes the published default (draft) and role semantics, which goes beyond a simple 'create' action.

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 well-organized with a summary sentence, an IMPORTANT note, and an Args list. Every line adds information without filler, making it both concise and structured.

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?

All 7 parameters are covered with practical details, including the important role-sync behavior. Since an output schema exists, the lack of return-value explanation is acceptable. This is a complete description for a moderately complex create tool.

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 schema has 0% description coverage, so the description fully compensates. Each argument is explained with its purpose (e.g., slug uniqueness, json_metadata contents, roles semantics including empty list = all users). This adds significant meaning beyond the bare schema types and defaults.

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 opens with 'Create a new dashboard,' a specific verb and resource. This clearly differentiates it from sibling tools like superset_dashboard_update, superset_dashboard_publish, and superset_dashboard_delete.

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 purpose is explicit: create a new dashboard. This implies when to use it versus other dashboard-related tools, but it does not explicitly name alternatives or state when not to use it, so it lacks full exclusionary guidance.

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