Delete Webhook

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

Adds context beyond annotations: in-flight retries dropped, past delivery preserved. Annotations already indicate destructive and idempotent, but description enriches with specific behaviors.

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?

Three sentences, front-loaded with purpose, then behavioral consequences. No wasted words.

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?

Complete for a simple delete tool: explains what is deleted, what stops, and what persists. No output schema needed.

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?

Single parameter with 100% schema coverage. Description does not add extra meaning beyond the schema's 'Webhook endpoint UUID to remove.' Baseline 3 is appropriate.

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: 'unregister a webhook endpoint'. Distinguishes from siblings like create_webhook, get_webhook. Explains side effects (no more events, dropped retries).

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?

Usage is intuitive from name and description, but no explicit when-to-use or when-not-to-use guidance compared to alternatives like rotate_webhook_secret.

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