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

Annotations already declare non-read-only, non-destructive, open-world behavior, and the description adds real value on top: the payload is a signed 'ping', the call fires immediately ('right now'), and it hits an external endpoint and returns an HTTP status. It doesn't cover failure/timeout semantics, but the safety and side-effect profile is well conveyed.

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 sentences, zero filler, with the action and its return value front-loaded and the usage note trailing. Every clause 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?

For a one-parameter action tool with no output schema, the description covers what it does, the payload semantics, and the returned value (HTTP status), and annotations cover the safety profile. Nothing material is missing.

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?

Single parameter with 100% schema description coverage; the schema already documents that 'id' comes from swop_list_webhooks. The description adds nothing parameter-specific, which is acceptable given 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 and resource ('POST a signed ping event to ... webhooks ... report the HTTP status'), naming the exact action and its observable result. It is clearly distinguishable from sibling webhook tools like swop_register_webhook, swop_list_webhooks, and swop_remove_webhook.

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?

'Use to confirm an integration before relying on it' gives a clear selection context for when to reach for this tool. It offers no explicit exclusions or named alternatives, but the purpose is narrow enough that alternatives aren't ambiguous.

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