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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with 'Permanently delete' plus adds a behavioral requirement not present in annotations: the need for explicit confirmation. It still omits whether deletion is reversible and what dependent data is affected, so it is good but not exhaustive.

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?

One compact sentence that leads with the action and appends the key constraint. Nothing is wasted, though the brevity leaves some behavioral detail unstated.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. Still, for a destructive two-parameter mutation with 0% schema description coverage, the description is thin on the confirmed parameter's exact semantics and any side effects of deletion.

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 must carry the parametric load. It maps loosely to both params — 'favorite chart' implies chartId and 'explicit confirmation' implies the confirmed boolean — but gives no format, type, or ID-source guidance, so it only partially compensates for the coverage 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?

States a specific verb+resource ('delete a favorite chart') in a single front-loaded clause, so an agent immediately knows the operation. It does not explicitly distinguish itself from siblings like delete_chart_channel_set or delete_custom_track, but the resource name is unambiguous enough that differentiation is implicit.

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?

'after explicit confirmation' hints at a precondition, implying the agent must obtain confirmation before invoking. However, it never states when to use this versus a listing tool like list_favorite_charts to resolve IDs, nor any exclusions, leaving usage context mostly implied.

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