superset_assets_export

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 the output format (ZIP, base64-encoded), the included asset types, and that database passwords are excluded. It does not explicitly state whether the operation is read-only, but 'export' inherently implies no mutation.

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 and well-structured: a clear top-line purpose, a list of contents, and a structured return format. Every sentence provides value, with no redundancy or filler.

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 zero-parameter, all-assets export tool, the description is fully complete. It explains what is included (dashboards, charts, datasets, connections), what is excluded (passwords), and the exact JSON response shape. The output schema further confirms this completeness.

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 tool has zero parameters, so there is nothing to clarify. The description adds meaningful context about the return value (format, encoding, data, size_bytes), which is useful beyond the empty schema. Baseline for 0 parameters is 4.

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 exports ALL Superset assets into a single ZIP file, specifying a distinct verb ('Export') and resource ('ALL Superset assets'). This differentiates it from sibling export tools that target individual asset types (e.g., superset_dashboard_export, superset_chart_export).

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 explicit use cases: 'Useful for backup or migration between instances.' It does not explicitly mention when not to use or contrast with alternatives, but the emphasis on 'ALL' and the list of included asset types makes the intended use clear.

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