retry_storage_delivery

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

Annotations already declare it is a non-read-only, non-idempotent operation; the description adds genuinely new context — that it writes to the selected bucket and requires storage:write plus owner/admin privileges. It stops short of noting side effects on existing delivery state or retry limits.

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, front-loaded sentences with no filler; the action, effect, and auth requirement each appear once and earn their 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 single-parameter mutation tool with annotations and no output schema, the description covers the operation, its write target, and auth requirements. The only gap is the delivery_id parameter, which the schema only partially covers via its pattern.

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?

With 0% schema description coverage, the description carries the burden of explaining delivery_id but says nothing about it beyond the tool's subject. The schema's regex pattern is the only source of format information, so the description adds no parameter meaning.

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?

"Requeue a failed or cancelled delivery" is a specific verb plus resource with a stated scope (failed/cancelled only). It clearly distinguishes itself from siblings like get_storage_delivery, list_storage_deliveries, and redeliver_webhook.

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 condition "failed or cancelled delivery" implies when to use it, but there is no explicit when-not guidance and no named alternative (e.g. redeliver_webhook or re-creating the delivery). Usage is inferable but not routed.

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