Delete a webhook endpoint (deliveries stop; history is kept)

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds real value beyond that by stating two consequences the annotations cannot express: deliveries stop and delivery history is retained rather than purged.

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 content is short but entirely duplicated: the title repeats the sentence and the description then restates it twice. The same clause ("deliveries stop; history is kept") appears three times across title and body, wasting the agent's attention.

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 one-parameter destructive tool with rich annotations and no output schema, the coverage is nearly adequate — the side effects are stated. It stops short of noting what happens on an unknown or already-deleted id, which matters for an idempotent delete.

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 single `id` parameter is documented in the schema with the `we_…` prefix hint. The description adds no meaning about the identifier beyond what the schema already provides, so the baseline applies.

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 names a specific verb and resource ("Delete a webhook endpoint"), so an agent can identify the operation immediately. It doesn't differentiate from nearby siblings like update_webhook_endpoint or list_endpoint_deliveries, but the delete semantics are 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?

There is no guidance on when to delete versus update or leave an endpoint inactive, and no mention of prerequisites such as confirming the endpoint id. The only usage-adjacent statement is the consequence that deliveries stop.

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