superset_delete_chart

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly identifies the destructive action and differentiates it from non-destructive dashboard removal. However, it does not mention permanence, required permissions, or side effects on dashboards, which prevents a perfect score.

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 two sentences with the action front-loaded in the first sentence. The second sentence adds a valuable distinction without redundancy, making it concise and well-structured.

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 one-parameter delete tool, the description covers the essential action, scope, and a common confusion (dashboard removal vs Superset deletion). An output schema exists, so return values are already defined; only deeper side-effect or error details are missing.

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?

With 0% schema description coverage, the description's 'by id' partially compensates by confirming that chart_id is the chart identifier. However, it adds little beyond the parameter name and integer type, and does not explain where to find the id or any format details.

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 uses a specific verb and resource: 'Delete a chart by id.' The second sentence clarifies that this is a Superset-level deletion, not just a dashboard removal, which distinguishes it from dashboard-related sibling tools.

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 explicitly states when not to use the tool: 'Removing it from a dashboard does not delete the chart.' It also directs the user to use this tool when the intent is to delete the chart from Superset, giving clear when/when-not guidance even though no alternative tool is named.

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