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

Annotations already declare destructiveHint=true, so the description's 'Delete' aligns with that. However, the description adds no context about irreversible effects, required permissions, or what happens to associated data. It merely restates the destructive nature already captured by annotations.

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, efficient sentence with no filler. It states the essential action and scope, making it appropriately concise and front-loaded.

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 operation, the description is adequate but minimal. It does not mention how to obtain the webhook_id (e.g., via list_webhooks), any prerequisites, or explicitly differentiate from the job-webhook deletion tool beyond the scope word. Given the tool's simplicity and the annotations covering destructive intent, this is a borderline acceptable level of 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?

Schema coverage is 50% (only 'id' has a description). The description adds no parameter information at all; it does not explain that 'webhook_id' identifies the webhook to delete or clarify the relationship between the two parameters. The description fails to compensate for the missing schema documentation.

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 states a specific verb ('Delete') and a clearly scoped resource ('company-scoped webhook'). This distinguishes it from sibling hires_delete_job_webhook, which targets job-scoped webhooks, so the purpose is 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?

No guidance is provided on when to use this tool versus alternatives like hires_delete_job_webhook or when not to use it. The only hint is the phrase 'company-scoped', which implies the scope but does not explicitly route the agent away from job-scoped webhooks.

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