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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation/safety profile is covered. The description adds genuine value beyond that: the observable consequence (the Public Delivery Page shows none) and the reversibility guarantee (restorable from presentation history). It stops short of stating failure behavior when no presentation exists.

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 tight sentences, with the primary effect front-loaded and the reversibility note second. No filler, no restatement of the title.

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 single-param destructive tool with annotations and no output schema, the description covers what is destroyed and that it is recoverable, which is the key context an agent needs. Edge cases like deleting when no presentation exists are unaddressed, keeping it just under a 5.

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?

Only one parameter (id) exists and schema coverage is 100%, so the schema already documents it fully. The description adds no extra meaning about the id beyond 'delivery', making the baseline 3 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?

States a specific verb (delete) and a precisely scoped resource (a delivery's current release presentation), and distinguishes itself from delete_delivery (which removes the delivery itself) by targeting only the presentation. An agent can tell exactly what is removed without opening the schema.

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 conveys intent (remove the current release presentation) but never states when to choose this over update_delivery_presentation or get_delivery_presentation, nor any prerequisite such as the delivery actually having a presentation. Usage is implied rather than specified.

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