list_webhook_deliveries

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

Annotations already mark readOnlyHint=true; the description reinforces this and adds meaningful behavior: secret values are redacted, up to limit records are returned, and dead-letter state is included. No contradiction with annotations. It doesn't cover ordering or pagination, but the added context exceeds the read-only annotation.

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 front-loaded, scannable, and free of filler. The Args section duplicates the schema's parameter description, but the rest of the description is efficient and well organized.

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 single-optional-param read-only tool with no output schema, the description conveys return contents, redaction behavior, and the limit default. It doesn't state ordering or pagination of deliveries, but the definition is largely self-sufficient.

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% since the limit parameter is fully documented with type, default, and description. The description's Args block and prose only restate 'maximum ... returns up to limit' without adding new constraints, formatting, or edge-case meaning, so the schema carries the weight.

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?

Description states a specific verb and resource: 'List redacted webhook delivery and dead-letter state.' It explicitly differentiates from siblings by saying test_webhook_destination triggers a send and list_webhook_destinations shows configured endpoints, so an agent can pick this tool for inspecting delivery history.

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?

Clear context: this read-only operation returns delivery records with status, attempts, and dead-letter state. It names sibling tools for related actions, but stops short of explicit when-not-to-use criteria or conditions for choosing this over a more general event list.

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