sheets_delete_chart

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

The annotation idempotentHint=true already signals that repeated deletes are safe. The description adds no extra behavioral context, such as whether the chart must exist, permissions required, or irreversibility. With annotations present, the bar is lower, but the description still does not go beyond the literal action.

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 a single, focused sentence with no filler or redundant information. It conveys the purpose efficiently.

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 two-parameter deletion tool with no output schema and an idempotency annotation, the description is minimally adequate. However, it omits potential edge cases (e.g., behavior if the chart ID is invalid, whether deletion cascades to associated data). The shortcoming is modest, given the tool's simplicity, but it does not fully help the agent anticipate outcomes.

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 description coverage is 100%, with both parameters already explained. The chartId description even provides a hint to use sheets_get_metadata. The tool description itself adds no parameter insight beyond what the schema provides, so the baseline 3 applies.

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 ('Delete') and resource ('chart from a Google Sheets spreadsheet'), clearly distinguishing it from siblings like sheets_create_chart and sheets_update_chart. It is unambiguous and action-oriented.

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 what the tool does but gives no explicit guidance on when to use it versus alternatives. The context of deleting a chart is clear from the name, but there is no mention of prerequisites, such as the chart belonging to the given spreadsheet, or exclusions. No comparison with sibling tools is provided.

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