delete_batch_webhook

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

Adds details beyond annotations: irreversible effect, cessation of callbacks, 404 error for invalid ID, authentication, rate limits (max 10 concurrent), and respect for read-only/dry-run modes. No contradictions.

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?

Well-organized: summary, then behavioral details, then Args. Each sentence adds value; no fluff. Front-loaded with purpose.

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?

Describes error handling (404), return values (JSON or empty body with 204), authentication, rate limits, and prerequisite tool call. With output schema present, return behavior is sufficiently covered.

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 coverage is 0%, but description provides complete parameter documentation: batch_webhook_id source (list_batch_webhooks) and account usage with configuration instructions. Adds essential 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?

Clear verb+resource: 'Delete a batch webhook permanently.' Distinguishes from siblings like delete_webhook and other delete tools by specifying 'batch webhook' and emphasizing permanence.

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 instructs to use list_batch_webhooks to find IDs, and warns of irreversibility. Lacks explicit when-not-to-use or alternatives like update_batch_webhook, but context is clear.

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