delete_webhook

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

No annotations are provided, so the description carries full burden. It states 'Delete a webhook' and 'Returns: Confirmation of deletion', which implies a destructive mutation but lacks details on permissions required, whether deletion is permanent, error conditions, or side effects. This is inadequate for a destructive tool with zero annotation coverage.

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 appropriately sized with three brief sections: purpose, args, and returns. It's front-loaded with the core action. However, the 'Args:' and 'Returns:' headings add minor structural overhead without enhancing clarity significantly.

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 this is a destructive mutation tool with no annotations, no output schema, and 2 parameters, the description is incomplete. It lacks critical behavioral details like authentication needs, irreversible effects, or error handling. The return value mention is vague ('Confirmation of deletion'), failing to specify format or content.

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 0%, so the description must compensate. It adds meaning by explaining 'repo_slug: Repository slug' and 'webhook_uuid: Webhook UUID (from list_webhooks)', clarifying the source of the UUID. This provides useful context beyond the bare schema, though it doesn't detail format constraints for repo_slug.

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 verb 'Delete' and resource 'a webhook', making the purpose unambiguous. It distinguishes from siblings like 'create_webhook' and 'list_webhooks' by specifying deletion, though it doesn't explicitly contrast with other deletion tools like 'delete_repository'.

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 guidance on when to use this tool versus alternatives. It mentions 'webhook_uuid: Webhook UUID (from list_webhooks)' which hints at prerequisite data, but offers no explicit when/when-not instructions or comparisons with sibling tools like 'delete_repository' or 'update_webhook' (if it existed).

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