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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context that secrets are redacted and approvals may apply, but it does not explain pagination behavior, delivery outcome fields, or what the approval requirements concretely enforce.

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 with the purpose front-loaded and little wasted text. The approval sentence is relevant but somewhat vague, so it is not maximally efficient.

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 output schema and annotations reduce some burden, but a five-parameter list endpoint with no parameter descriptions needs more invocation context than this. The description omits how to filter, paginate, or relate the required webhookId to the returned deliveries.

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?

There are five parameters and 0% schema description coverage, yet the description names none of them. It does not clarify webhookId, id, limit, offset, or search semantics, leaving the agent unable to infer filtering or pagination behavior from 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?

States a specific read action and resource: webhook delivery outcomes. It is distinguishable from mutation-focused webhook tools, but it does not explicitly contrast with siblings like list_organization_webhooks or get_organization_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?

The description implies it is used to inspect delivery outcomes, but gives no explicit when-to-use guidance, exclusions, or alternatives among the webhook-related tools. The approval sentence adds policy context rather than usage guidance.

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