delete_webhook

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

Discloses irreversible action, authentication method, rate limit (max 10 concurrent requests), read-only/dry-run mode respects, and error condition (404 for invalid IDs). Without annotations, this comprehensive behavioral info is critical and well-provided.

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?

Structured efficiently with a clear purpose sentence, followed by separate sections for behavioral notes, auth, args, and returns. No wasted words; each sentence adds essential 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?

Given the tool has 2 required parameters and no annotations, the description covers all critical aspects: purpose, when to use, parameters, error handling, and return format. Output schema exists but description still summarizes return JSON.

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 fully explains both parameters: list_id (type, length, format, example, origin) and webhook_id (origin). Adds substantial meaning beyond the minimal schema.

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?

The description clearly states the action ('Delete a webhook') and the effect ('immediately stopping event notifications'). It uniquely identifies the resource and distinguishes from sibling tools like create_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?

Explicitly tells when NOT to use (if wanting to pause, as no pause mechanism exists) and what to use instead (create_webhook for replacement). Provides clear usage context.

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