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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context: 'bounded' signals pagination, 'without payloads' sets expectations about returned data volume, and 'coarse failure reasons' indicates the granularity of failure information. It does not, however, describe pagination mechanics or any auth/permission requirements beyond what annotations imply.

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 a single, front-loaded sentence with no wasted words. However, for a tool with four parameters and low schema coverage, the extreme brevity borders on under-specification rather than optimal conciseness.

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 tool has an output schema, so the description need not explain return values; it does, however, usefully summarize the returned data ('status codes, coarse failure reasons, without payloads'). Annotations cover the safety profile. The remaining gap is the lack of any parameter guidance or usage context, which is a notable omission given only 25% schema description coverage.

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 only 25% (only organization_id is described in the schema), so the description must compensate. It does not mention any parameter by name or explain how webhook_id, page, page_size, or organization_id affect the operation. The word 'bounded' vaguely hints at pagination but adds no concrete semantic detail beyond what the schema already provides via types and defaults.

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 ('List') and resource ('delivery attempts, status codes, and coarse failure reasons'), clearly distinguishing this from list_webhooks by focusing on delivery attempts rather than webhook definitions. The scope constraint 'without payloads' further sharpens the purpose. It stops short of naming a sibling alternative explicitly, so a 5 is not warranted.

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?

No guidance is provided on when to use this tool versus alternatives like list_webhooks, get_webhook, or test_webhook. There are no prerequisites or exclusion conditions mentioned. The agent must infer usage from the purpose alone.

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