Resume a webhook destination

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description does add one genuine behavioral detail beyond structured data — that pending deliveries are included, not just future ones — but says nothing about permissions, timing, or effects on previously failed deliveries.

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?

A single efficient sentence that front-loads the action. Nothing is wasted, though it is arguably a touch thin for a mutating operation.

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?

Annotations carry the safety profile and no output schema exists, so the description needn't explain returns. However, for a state-changing endpoint it omits the required id's role and any consequence for deliveries that were already dropped, leaving a modest gap.

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% for two parameters, so neither 'id' nor 'debug' is explained anywhere. The description provides no parameter meaning at all, leaving the agent to guess what 'debug' does.

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?

Specific verb+resource: resume deliveries to a paused webhook destination, with the extra scope of pending deliveries. It clearly stands apart from pause_delivery_destination, though it doesn't name that sibling explicitly.

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 phrase 'to a paused webhook destination' implies the precondition for use, so context is implied but never stated as an explicit rule. No alternative tool is named for the opposite action.

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