Recent delivery attempts for one webhook endpoint (status, attempts, last error) — the first place to look when events aren't arriving.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max deliveries to return (1..=200, default 50). | |
| webhook_id | Yes | Webhook endpoint id (uuid). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses the read-only nature (querying delivery history) and returned fields, but does not specify recency limits or pagination. Adequate but could be more detailed.
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?
Single sentence, front-loaded with purpose and key details. No wasted words.
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?
No output schema, so description should detail return value structure. It mentions fields but lacks specifics on whether it returns a list or single item, and pagination. Nevertheless, sufficient for a simple diagnostic tool.
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 covers 100% of parameters with descriptions. Description adds minimal value beyond implying webhook_id is the endpoint identifier. Baseline 3 is appropriate.
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 clearly states it returns recent delivery attempts for one webhook endpoint, listing fields (status, attempts, last error) and providing a usage context ('first place to look when events aren't arriving'), distinguishing it from diagnostic siblings like test_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?
Explicitly suggests using this tool for troubleshooting failed deliveries, but does not mention when not to use it or alternative tools like test_webhook for testing. Good context but lacks exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.