superset_dashboard_copy

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

No annotations are present, so the description carries the transparency burden. It adds useful behavioral detail by noting that Superset requires json_metadata (defaulting to '{}') and that the copy includes 'all its charts'. However, it does not disclose whether the copy is published, how permissions are handled, or what happens if the source dashboard is missing.

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 compact and front-loaded with the main purpose, followed by a simple parameter list. Every sentence adds value, with no redundant or vague wording.

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 tool has an output schema, so return-values need not be described. The description covers all parameters, notes a crucial requirement (json_metadata), and clearly states the tool's scope. Minor gaps remain (e.g., prerequisites or error behavior), but overall it is complete enough for correct invocation.

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 Args section elaborates on all three parameters: dashboard_id is the source, dashboard_title is the new title, and json_metadata is the JSON metadata with an important note. Since the schema has no descriptions (0% coverage), this fully compensates and adds semantic meaning.

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 tool's purpose with a specific verb ('Create') and resource ('a copy of an existing dashboard with all its charts'). This distinguishes it from sibling tools like superset_dashboard_create (new dashboard) and superset_chart_copy (single chart), making the intent unambiguous.

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 context for when to use the tool: when you need to duplicate an existing dashboard. It does not explicitly name alternatives, but the 'existing dashboard' qualifier and mention of charts make the use case clear, without needing to exclude other tools.

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