list_webhook_deliveries

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the action and plan restriction, omitting crucial details like whether the tool lists deliveries across all webhooks or per webhook, what the response format looks like, and whether there is pagination or rate limiting. This is a significant gap for an agent understanding the tool's behavior.

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 that says exactly what the tool does and includes the relevant Business plan condition. Every word earns its place; no unnecessary filler.

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 is simple (no parameters, no output schema), but the description does not explain what the return value represents or whether it scopes to a particular webhook. It is minimally viable but leaves uncertainty about the response shape and scope, especially given the lack of annotations.

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 tool has zero parameters, so the baseline is 4. The empty input schema already says there are no parameters; the description doesn't need to add more. The 'Business plan' note is unrelated to parameters but does not hurt.

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 ('List') and resource ('webhook deliveries'), clearly distinguishing it from sibling tools like list_webhooks. The parenthetical '(Business plan)' adds a relevant plan restriction, making the purpose unambiguous.

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 usage for listing webhook deliveries and mentions a Business plan requirement, but it does not explicitly state when to use this over alternatives (e.g., list_webhooks) or provide exclusions. The guidance is inferred rather than stated.

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