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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description adds genuinely useful scope information: existing job delivery records are retained and no new deliveries are sent. It effectively tells the agent the destruction is partial rather than a hard purge, which annotations alone cannot convey. It stops short of stating permission requirements or behavior when the id is unknown.

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 short sentences, front-loaded with the primary effect (stop deliveries, forget the destination) and followed by the retention caveat. Every clause earns its place.

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 one-parameter destructive tool with rich annotations and no output schema, the description covers the essential behavioral question: what happens to already-referencing jobs. Missing only minor details such as the error/behavior for an unknown destination id or required authorization, which the idempotent hint partially covers.

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% and the sole parameter's schema description even points at render.destination.list as the id source, so the schema carries the load. The description adds no format or id-resolution detail beyond that. Baseline 3 is appropriate.

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 specific effect on a specific resource: deliveries to the destination stop and the destination is removed. It distinguishes itself from siblings such as render.destination.test (which also touches deliveries) and render.destination.list/create by describing a permanent removal rather than a probe or a creation.

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?

Usage is implied — call this when you want to stop deliveries and drop the destination — but no explicit when/when-not condition or alternative (e.g. test the destination first, or check jobs still naming it) is offered. Note the description does clarify that jobs already naming it are unaffected, which nudges toward a 'safe to delete anytime' reading.

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