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

No annotations exist, so the description carries the full burden. It does disclose genuinely useful behavior: the 'stub or live' distinction and the 'HMAC when secret set' security detail, plus read-only nature implied by 'List'. However, phrases like 'No DID sales', 'KVKK', and 'Advanced: own PBX/Asterisk stays on customer' are marketing/legal noise that do not describe tool behavior.

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 core sentence is front-loaded and tight. But the trailing run of terse phrases — 'Idle $0. No DID sales. KVKK. Advanced: own PBX/Asterisk stays on customer.' — does not earn its place for an agent deciding whether to call the tool, diluting an otherwise compact definition.

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 low-complexity list tool with two optional parameters, the description covers purpose, endpoint, and security (HMAC). Yet with no output schema present, the return format/pagination of the delivery log is never described, and the noise phrases crowd out actionable context, leaving it adequate but with clear gaps.

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 coverage is 100%, so the schema already documents limit and webhook_id. The description's endpoint example '?limit=20&webhook_id=' merely echoes the schema defaults rather than adding new meaning, so it stays at the baseline 3 with no added parameter insight.

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: 'List last N outbound webhook deliveries'. The scope is sharpened with '(stub or live)' and the delivery categories 'promise/fact/orchestra/redact/ping'. Purpose is clear and the name (deliveries vs the sibling pbx_webhooks) implies a log-of-deliveries distinction, though it never explicitly contrasts with pbx_webhooks.

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?

Usage is implied rather than stated — an agent can infer 'use this when you want to inspect the outbound delivery log' from the verb and the 'Durable log of Temsor→customer POSTs' line. However, it never names an alternative (e.g. pbx_webhooks for configuration) nor states any when-not-to-use condition, so routing decisions are left to inference.

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