superset_chart_delete

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

With no annotations, the description carries the burden. It discloses the key side effect (removal from all dashboards) and emphasizes that confirm_delete is required, revealing a safety mechanism. However, it does not mention irreversibility, permission requirements, or what happens if confirm_delete is false, leaving some behavioral gaps.

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 extremely concise, consisting of one purpose sentence and a bullet-like list of parameters. Every element serves a purpose with no 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?

For a simple delete operation, the description provides the necessary facts: what is deleted, the impact on dashboards, and the need for confirmation. The presence of an output schema reduces the need to describe return values. However, the ambiguous treatment of confirm_delete (schema says optional, description says required) could confuse an agent, so it is not fully complete.

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?

Schema coverage is 0%, so the description is the sole source. It defines chart_id as the ID of the chart and confirm_delete as a required confirmation, which adds meaning. It doesn't specify that confirm_delete must be true to proceed, but the 'REQUIRED' label provides essential context.

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?

Description clearly states 'Delete a chart by ID' and explicitly notes the side effect of removal from all dashboards, distinguishing it from other chart operations like update or get. This is a specific verb+resource with clear scope.

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?

No guidance is provided on when to use this tool versus alternatives like superset_dashboard_delete or superset_chart_update. The description merely states the action without any conditions, prerequisites, or situations where this tool should or shouldn't be used.

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