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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context: it returns payloads and retry history, and it requires a Proof account with a specific authentication workflow. However, it does not state whether the operation is read-only, what happens for an invalid/nonexistent ID, or any response format details, which a full disclosure would include.

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 two sentences, both purposeful: the first defines the tool's behavior and scope, the second provides a necessary authentication prerequisite. There is no wasted wording, and the most important behavioral information is front-loaded.

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 simple one-parameter read tool, the description is adequate: it states what the tool does and the access requirement. However, it lacks any guidance on when to choose this over sibling webhook tools, does not describe the return structure (no output schema exists), and omits error/edge-case behavior. These are notable gaps for an agent invoking the tool.

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% and the description adds no information about the 'id' parameter beyond the schema's 'Webhook delivery ID.' Since the schema already documents the only parameter, the baseline score of 3 applies; there is no additional semantic enrichment in the description.

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 states a specific verb ('Get details') and resource ('a single webhook delivery attempt'), and explicitly scopes the content to 'request/response payloads and retry history.' The word 'single' differentiates it from sibling tools like list_webhook_deliveries and get_webhook_stats, so an agent can identify what this tool uniquely does.

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?

The description gives an ACCESS note that authentication is required and that start_login does not open this tool, but it does not explain when to use this tool versus alternatives such as list_webhook_deliveries or retry_webhook_delivery. There is no explicit when-to-use or alternative selection guidance, leaving that to inference.

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