pause_webhook

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

Discloses key behaviors: write operation, non-destructive to attachments, polling behavior. No annotations exist, so the description carries the transparency burden and does it fairly well, though it omits details like idempotency or error handling.

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?

Extremely concise: one-sentence description plus a clarifying phrase. No redundant information.

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 simple one-parameter tool without annotations or output schema, the description covers the primary action and a notable behavioral nuance. Minor gaps like error scenarios or defaults are acceptable given the tool's simplicity.

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 with 100% schema coverage; the description does not add additional meaning beyond the schema's 'Webhook subscriber UUID'.

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?

Clearly states the action 'Pause deliveries' and the resource 'webhook subscription'. Distinguishes from sibling 'resume_webhook' by indicating the pause is temporary until resumed.

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?

Provides context that attachments persist and the poller skips, but lacks explicit guidance on when to use this vs. alternatives like delete or when not to use. The relation to resume_webhook is implied but not stated.

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