superset_dashboard_import

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 that overwrite controls replacing existing objects with the same UUID, and that files must be YAML-based. However, it does not specify default behavior when overwrite=False (e.g., error vs skip) or other side effects like dependency imports.

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 only three short sentences plus a brief arg list. It front-loads the main purpose and keeps parameter explanations minimal, earning its place without redundancy.

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 complexity of an import operation with dependencies and overwrite semantics, the description covers the essentials but omits return value details, failure handling, and default behavior when overwrite=False. The lack of explicit usage guidance for alternatives also leaves a gap.

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 lacks property descriptions (0% coverage), but the description compensates with an Args block defining file_path as an absolute path and overwrite as a toggle for existing UUID objects. This adds meaning beyond the bare types in the schema.

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 'Import dashboards from a ZIP file (created via export),' clearly stating a specific verb and resource. It distinguishes from sibling tools like superset_dashboard_export and superset_chart_import by specifying dashboards and ZIP input.

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?

It provides clear context: the ZIP should come from an export and contain YAML dashboard/dependency files. However, it does not explicitly state when to choose this tool over superset_assets_import or superset_chart_import, nor does it list exclusions.

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