Contract Testing: Delete Webhook

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows it's a destructive but idempotent operation. The description adds no further behavioral context (e.g., whether deletion is irreversible, error behavior on missing UUID). With annotations covering the safety profile, a 3 is appropriate.

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 very short and front-loaded with the core action. It includes a 'Toolset' header for grouping, which is helpful. However, it could be slightly more structured (e.g., separating purpose from toolset). Still, it is concise and earns its place.

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, no output schema), the description covers the minimal needed. It does not mention return behavior (e.g., success/error responses) or edge cases, but for a simple delete operation it is sufficient. No output schema exists to compensate.

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 100%, and the description reproduces the same parameter details (webhookId, string, required, UUID). It adds no additional meaning beyond what the schema provides, meeting the baseline.

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 'Delete a webhook by UUID.' The verb 'delete' and the resource 'webhook' are specific. Among siblings like create, update, get, and execute webhook, this tool is immediately distinguished as the deletion operation.

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 gives the action but offers no guidance on when to use it versus alternatives (e.g., when to delete vs update). It does not mention prerequisites or typical scenarios, but it is implied as the tool to remove a webhook.

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