superset_dashboard_delete

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly warns 'CRITICAL: the dashboard will be permanently deleted' and clarifies the deletion scope, which is essential for a destructive operation. This goes beyond the minimal 'delete' phrasing.

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 one-line purpose, a critical warning, and a short Args list. Every sentence earns its place without fluff or repetition.

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 delete tool with an output schema, the description sufficiently covers the essential context: the deletion scope, permanence, and the required confirmation parameter. It does not need to explain return values because the output schema handles that, and there are no other complex behavioral aspects.

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 describes both dashboard_id and confirm_delete, adding meaning beyond the schema. It labels confirm_delete as 'REQUIRED', which clarifies that the flag must be set true to actually delete—an important behavioral detail the schema alone (with default false and not in required) does not convey.

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 'Delete a dashboard by ID', a specific verb and resource that clearly distinguishes it from sibling tools like get, update, copy, or list. The scope is further clarified by stating charts and datasets are not deleted.

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 states when to use the tool (to delete a dashboard) and provides a clear exclusion by noting that charts/datasets are not deleted. However, it doesn't explicitly name alternative tools for those cases, falling short of a full when/when-not/alternatives explanation.

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