delete_webhook

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

Annotations already declare destructiveHint=true, so the description adds a bit by saying 'permanently delete' and linking force to permanence. However, it does not clarify the actual default (force=true per schema) or consequences of setting force=false, creating potential confusion about behavior beyond the annotation.

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?

Two short sentences, immediately front-loaded with the core action. No redundant words or filler, making it easy for an agent to parse quickly.

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 delete tool with no output schema, the description covers the essential action. However, it misses clarification on the force default discrepancy (schema default true vs. description implying true is special) and does not mention what the response contains, even though a 'fields' parameter exists. The description is adequate but not fully complete.

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 100%, so all parameters are already described. The description's 'Set force=true to permanently delete' merely repeats the schema's force description without adding new meaning. No additional parameter context is provided beyond the 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 'Delete a webhook' with a specific verb and resource. It distinguishes from sibling webhook tools (list/get/update) and other delete_* tools by naming the target resource. The mention of force=true adds relevant detail without obscuring the primary action.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., update_webhook to disable, or soft delete). The only hint is the force parameter, but the description does not explain when it should be set or the default behavior. This leaves the agent to infer usage context.

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