delete_webhook

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

No annotations provided, so description carries full burden. It indicates deletion but does not discuss idempotency, error handling for non-existent webhooks, or any side effects beyond the operation.

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?

The description is well-structured with headings (Prérequis, Args, Returns) and is concise. Every sentence adds value, though the blank line before Args could be omitted.

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 simplicity of the tool (2 params, no nested objects), the description covers prerequisites, parameters, and return type. With an output schema and sibling tools, it is sufficiently complete, though it could explicitly differentiate from clear_webhook_queue.

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 adds meaning by explaining each parameter: doc_id as document ID and webhook_id as the ID of the webhook to delete. This compensates for the schema's lack of descriptions.

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 explicitly states 'Supprime un webhook' (delete a webhook), which is a specific verb and resource. It clearly distinguishes from sibling tools like create_webhook, modify_webhook, clear_webhook_queue.

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 a clear prerequisite calling list_webhooks to obtain a valid webhook_id, guiding usage. Does not explicitly state when not to use, but the context of deletion is straightforward.

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