Webhook.site MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions deletion but doesn't specify whether this is irreversible, requires specific permissions, has rate limits, or what happens to filtered-out requests. The destructive nature is implied but not explicitly warned about.

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 efficiently conveys core functionality with optional parameters mentioned. No wasted words or redundant information, making it easy to parse quickly.

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 destructive operation with no annotations and no output schema, the description is insufficient. It doesn't address critical context like irreversible deletion, permission requirements, confirmation prompts, or what constitutes a successful deletion. The optional filtering is mentioned but without behavioral implications.

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 100%, providing complete parameter documentation. The description adds marginal value by mentioning optional filtering by date range or query, which aligns with schema parameters but doesn't provide additional semantic context beyond what's already in the schema descriptions.

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 action ('Delete all requests') and resource ('from a webhook'), with optional filtering parameters mentioned. It distinguishes from sibling 'delete_request' by specifying bulk deletion, but doesn't explicitly contrast with other webhook management tools like 'delete_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?

No guidance on when to use this tool versus alternatives like 'delete_request' (single deletion) or 'delete_webhook' (entire webhook removal). The optional filtering is mentioned but without context about when filtering is appropriate versus full deletion.

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