delete_webhook

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It does not disclose the destructive nature of the operation (beyond the verb 'delete') or mention any irreversible consequences, error conditions, or required permissions. The description is minimal and leaves much to inference.

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 a single, short sentence that is immediately clear and front-loaded. No wasted words; it is concise yet sufficient given the tool's simplicity.

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?

The tool is a simple delete operation with one parameter and no annotations. The description is too sparse to be complete: it lacks any context about error handling, idempotency, or the effect of deleting a webhook (e.g., whether it is permanent). Given the availability of an output schema, it might be sufficient for a basic call, but the lack of usage and behavior details makes it incomplete.

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%, and the description provides no additional detail about the 'webhook_id' parameter beyond its name in the schema. It doesn't explain what the ID looks like, how to obtain it, or any constraints (e.g., format, ownership). Given the single parameter, this is a significant gap.

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') and the resource ('a webhook') with a specific identifier ('by ID'). It is unambiguous and distinguishes it from other webhook operations like create_organization_webhook or list_organization_webhooks, though it doesn't explicitly name siblings.

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?

The description implies that the tool is for deleting webhooks but does not provide explicit guidance on when to use it versus other webhook-related tools, nor does it mention any prerequisites (e.g., that the webhook must exist or that the user must own it).

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