listWebhookEvents

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only (GET)' and the rate limit of 100 requests per 1m, providing safety and throttling context. It does not mention pagination or auth, but the core behavioral traits are disclosed.

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 that front-loads the action, then provides the rate limit and endpoint. Every clause adds value, with no filler or redundancy.

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 description covers the core purpose, read-only semantics, and rate limiting, which is enough for basic understanding. However, with no output schema and no parameter documentation, an agent cannot fully determine valid status or event_type values without external guesswork.

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 0%, and the description does not mention any of the four parameters. 'limit' and 'offset' are somewhat self-evident, but 'status' and 'event_type' have no documented allowed values or meaning, leaving a significant gap.

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 uses a specific verb and resource: 'List webhook delivery events.' It adds the HTTP method and endpoint path, which makes the tool's role unmistakable and distinguishes it from sibling tools like getWebhooks or listTransactions.

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 clearly states what the tool lists and that it is read-only, but it does not explicitly say when to choose this tool over sibling tools or when not to use it. Usage is implied by the resource name rather than explicitly contrasted with alternatives.

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