superset_dashboard_export

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

With no annotations, the description carries the full burden and does disclose key behavioral traits: output is a base64-encoded ZIP, includes all dependencies, and can be re-imported. This is transparent about the return format and scope, though it does not mention permissions or size limits.

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 tight and well-structured, leading with a one-sentence summary, then a brief note on importability, followed by Args and Returns sections. No unnecessary words or duplication.

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?

Given the single parameter and the fact that an output schema is described inline, the description covers input, output format, dependencies, and reuse path. It is complete for a straightforward export tool, with no required missing details.

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 sole parameter 'dashboard_ids' is described with a concrete format (comma-separated IDs) and an example, compensating fully for the schema's lack of description. This is beyond what the raw 'string' type provides.

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 states a specific verb 'Export' plus resource 'dashboards' and clearly scopes the action to include dependencies (charts, datasets, databases). It distinguishes from similar tools like superset_dashboard_get or superset_assets_export by highlighting the ZIP export and import compatibility.

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 clearly indicates this tool is for exporting dashboards for reuse via superset_dashboard_import, establishing a primary use case. It does not explicitly mention alternatives or exclude cases, but the context is sufficient for basic selection among dashboard-related siblings.

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