Contract Testing: Delete Webhook

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

The description contradicts the annotations: it claims the tool deletes a webhook (destructive action), but annotations set readOnlyHint=true and destructiveHint=false. Additionally, no other behavioral traits (e.g., permissions, irreversibility) are disclosed.

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 efficient, using two sentences plus a simple parameter list. It is well-structured and front-loaded with the action, though the 'Toolset: Webhooks' line could be integrated.

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 description and annotations together fail to provide complete context. The contradiction between description and annotations is a major gap. There is no output schema, and the description does not address return values or side effects.

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 description repeats the parameter information already present in the input schema (webhookId as required UUID). Since schema coverage is 100%, the description adds no extra meaning, meeting the baseline but not exceeding it.

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', which is specific and distinguishes it from other webhook tools like create, get, update, and list. However, the clarity is undermined by the annotation contradiction where readOnlyHint is true, conflicting with the delete action.

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 does not mention prerequisites, exclusions, or context for deletion.

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