Charts: delete

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

Annotations already declare destructiveHint=true, but the description adds concrete consequence detail beyond that: dangling empty widgets remain on dashboards, deletion is permanent, and it warns to check with the user first. It does not discuss auth requirements or reversibility beyond 'permanently,' which slightly caps the 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?

Four sentences, mostly informative, but the follow-up instruction ('find the widgets...clear them') is operational guidance rather than purpose-defining and somewhat pads the length. Front-loaded well with the core action first.

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?

No output schema, so the description notes it returns JSON, though not the shape. Covers the mutation, the side effect on dashboards, and the safety warning. Sufficient for an agent to call it correctly given annotations already flag destructiveness.

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 100%, giving a baseline of 3; the description adds the operational constraint that the chart ID is required but the schema already says that too. The description's 'find it with charts_list' is already in the schema's parameter description, so no extra value there, but the schema itself is complete.

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?

States a specific verb ('Delete') and resource ('chart'), plus the permanent nature of the removal. Explicitly distinguishes itself from the more surgical dashboards_remove_widget by contrast.

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?

Gives explicit when-to-use and when-not-to-use: 'To take a chart off one dashboard but keep it, use dashboards_remove_widget instead.' Also prescribes a follow-up workflow (find dangling widgets via dashboards_get, clear with dashboards_remove_widget).

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