list_webhook_deliveries

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

No annotations are provided, so the description must carry the full burden. It merely says 'List' which implies a read operation, but does not disclose pagination behavior, ordering, scoping (beyond the optional endpoint_id), or what fields the delivery log entries contain. Significant behavioral details are missing.

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, focused sentence with no redundant words. It front-loads the verb and resource, conveying the core purpose efficiently.

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?

Given the lack of an output schema and annotations, the description is insufficiently complete. It does not explain what the webhook delivery log contains, how results are ordered, how pagination works, or even that it is a read-only operation. For a list tool, more context is expected.

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?

The input schema provides full descriptions for both parameters (limit and endpoint_id), so the description adds little beyond what the schema already specifies. With 100% schema coverage, the baseline of 3 is appropriate; the description does not enrich the parameters' meaning.

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 clearly states the tool's action ('List') and resource ('webhook delivery log'), and it is distinct from sibling tools like list_webhook_endpoints, which list endpoints rather than delivery logs. The purpose is immediately understandable.

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?

There is no guidance on when to use this tool compared to alternatives. It does not mention scenarios, exclusions, or related tools such as list_webhook_endpoints or create_webhook_endpoint. The usage context is only implied by the name.

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