chart_delete

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

Annotations already declare destructiveHint=true, so the agent knows this is destructive. The description adds that it is 'Undoable' but removes the chart and its formatting, providing extra context about reversibility and side effects. This goes beyond the annotations and adds value without contradicting them.

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?

Two concise sentences with zero fluff. The action is front-loaded, and the prerequisite instruction is directly relevant. No redundant phrasing.

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 tool, the description covers the main intent and the chartId source, but it fails to explain the sheetIdx parameter, which is required. No output schema exists, so return behavior is not specified, but that might be acceptable for a delete operation. The missing sheetIdx explanation is a notable 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?

Schema coverage is 50%: only chartId has a description ('From chart__list'), while sheetIdx has none. The description clarifies chartId by repeating the schema hint, but it offers no explanation for sheetIdx. Since half of the parameters are undocumented in both schema and description, the description only partially compensates for the gap.

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 states a clear action: 'Delete a chart.' This is specific to a chart resource and distinctly different from siblings like chart_insert, chart_list, chart_update, and chart_from_block. An agent can immediately identify this as the deletion operation without confusion.

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 instructs to 'Get the chart_id from chart__list,' which provides a clear prerequisite for usage. It doesn't explicitly mention alternatives or exclusions, but the context of deletion is unambiguous. It implies that chart_list should be used first, which is helpful guidance.

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