Pause a webhook destination

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds real behavioral value beyond that by disclosing what happens to in-flight work: pending deliveries are held rather than dropped, which matches destructiveHint=false and tells the agent this is reversible. It still says nothing about permissions or rate 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?

A single sentence that front-loads the action and immediately qualifies its scope. 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 state-mutation tool with no output schema, the description adequately conveys the effect on new and pending deliveries. However, it leaves the `debug` parameter completely unexplained and gives no signal about what a successful pause returns or how to confirm the new state.

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% across two parameters. The description never mentions the required `id` or the optional `debug` flag, so an agent gets no guidance on what `debug` changes or what format `id` takes. With two undocumented parameters, the description fails to compensate for the coverage gap.

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 ("Stop new deliveries to a webhook destination") and even hints at the inverse operation via "until it resumes," which points at resume_delivery_destination. It is clear on its own but never names the sibling, so an agent must infer the pairing.

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 clause "pending ones wait until it resumes" implies this is the pause half of a pause/resume pair, giving implied usage. There is no explicit statement of when to pause versus cancel or retry dead-letter deliveries, nor any prerequisites.

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