Superset MCP Integration

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the API endpoint ('/api/v1/dashboard/ POST') which is useful context, and states it 'creates a new dashboard' which implies a write/mutation operation. However, it doesn't disclose important behavioral traits like authentication requirements, error conditions, rate limits, or what happens on duplicate titles. The return format is mentioned but without structural details.

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-structured with clear sections (purpose, endpoint, args, returns) and uses bullet points effectively. Every sentence adds value: the first states the purpose, the second provides implementation context, and the parameter/return sections document essential information. It could be slightly more concise by combining some elements, but overall it's efficient.

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 creation tool with 2 parameters, no annotations, and no output schema, the description provides basic but incomplete coverage. It documents the parameters well and mentions the return type, but lacks crucial context about authentication, error handling, and behavioral constraints. Given the mutation nature of the operation and the complexity implied by 'json_metadata' (a nested object), more guidance would be helpful.

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?

With 0% schema description coverage, the description must compensate for the schema's lack of parameter documentation. It provides meaningful explanations for both parameters: 'dashboard_title: Title of the dashboard' and 'json_metadata: Optional JSON metadata for dashboard configuration, can include layout, color scheme, and filter configuration'. This adds substantial value beyond the bare schema, though it doesn't specify format constraints or examples.

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 dashboard in Superset' which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'superset_dashboard_update' and 'superset_dashboard_delete' by focusing on creation. However, it doesn't explicitly differentiate from other creation tools like 'superset_chart_create' or 'superset_dataset_create' beyond the resource type.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like authentication), when creation is appropriate versus updating existing dashboards, or how it relates to other dashboard operations like listing or getting by ID. The agent must infer usage from the tool name alone.

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