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

Annotations already flag destructiveHint=true and idempotentHint=false, so irreversibility is partly covered; the description adds the non-obvious behavioral detail that the user is prompted before deletion and that the shape is unrecoverable. That confirmation flow is information the annotations do not convey.

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?

Three short sentences, front-loaded with the verb, and no filler. Slight redundancy between 'cannot be undone' and 'not recoverable' costs a point.

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 exists and none is needed for a delete; the description covers irreversibility, the confirmation requirement and workflow continuation, which is strong for a simple 2-parameter mutation. It falls short only on parameter meaning and a success/failure signal.

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 0% and the description adds nothing about either parameter. It does not explain that 'id' identifies the drawing or what the optional 'symbol' scopes, so the zero-coverage schema is left uncompensated.

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 and resource ('Delete a drawing') that is unmistakably distinct from siblings like drawing_add, drawing_freehand and drawing_style. The opening sentence alone tells an agent exactly what the tool does.

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 clear operational context: deletion requires the user to be asked first, and names follow-up routes (chart_link for a finished chart, analysis_prepare for a shared draft). It does not spell out when *not* to use it versus e.g. drawing_style, but the workflow guidance is actionable.

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