delete_webhook

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It simply states 'Delete a webhook' without mentioning whether the deletion is permanent, irreversible, or requires special permissions. This is a minimal disclosure lacking side effects or consequences.

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, clear, and direct sentence with no unnecessary words. It is appropriately sized for a simple delete operation and is front-loaded with the core action.

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 low complexity (one parameter, full schema coverage, no output schema), the description is adequate but not fully complete. It lacks any mention of return value, side effects, or dependencies, though these are less critical for such a straightforward delete tool. A bit more context about consequences would improve completeness.

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?

The schema has 100% coverage for the single parameter 'id', which is described as 'ID of the resource'. The description adds no additional meaning beyond the schema, which is already sufficient for this simple one-parameter tool.

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 'Delete a webhook' clearly states the specific verb (delete) and resource (webhook), making it distinct from sibling tools like list_webhooks, get_webhook, create_webhook, and get_webhook_logs. It is concise and unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives, such as when to list or get webhooks. The usage context is implied by the verb 'delete' but no alternatives or exclusions are mentioned.

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