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

Adds substantial context beyond annotations: the payload is a signed `ping`, the call is a real outbound request with no retry, the response includes HTTP status and body, and it requires the `webhooks:write` scope. This aligns with openWorldHint=true and idempotentHint=false rather than contradicting them.

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?

Two tight sentences: behavior and return value first, then the safety/authorization caveats. No filler.

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?

Even without an output schema, the description explains what is returned (HTTP status and body) and the risk profile (live request, no retry, required scope). An agent has everything needed to call it correctly.

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?

Only one parameter and the schema documents it fully (whe_... id from list_webhook_endpoints), so the description adds nothing on parameter semantics. Baseline 3 for full schema coverage.

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?

States a specific verb (send a signed ping) and resource (one webhook endpoint) plus the immediate effect (return the receiver's answer). Clearly distinguishable from siblings like list_webhook_endpoints and list_webhook_deliveries.

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?

Makes the key condition explicit — it sends a real request to the customer's address right now and is not retried — which tells the agent this is a one-shot live probe, not a queued job. It does not explicitly contrast with test_integration or say when not to use it, so it falls short of 5.

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