delete_all_requests

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. While 'Clear captured events' implies deletion, it does not mention that the action is irreversible, the full scope (all matching requests), or any confirmations/undo options. The description's 'reset an inbox' metaphor is helpful but insufficient for a destructive operation.

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 exceptionally concise: two sentences that quickly convey the action and a primary use case. Every word earns its place with no fluff.

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?

Despite having an output schema and four parameters, the description lacks key details for a destructive operation: it does not state that the deletion is permanent, that it applies to all captured events for the webhook, or any safety mechanisms. The use-case sentence helps but is not enough to fully understand the tool's impact.

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 input schema only documents 'webhook_token' (25% coverage). The description adds that clearing can be optionally filtered 'by date or search query', which partially explains the purpose of 'query', 'date_from', and 'date_to'. However, it does not specify the date format, query syntax, or how these parameters interact, leaving significant ambiguity.

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 ('Clear captured events on a webhook') and the optional scoping by date or search query, which makes the core purpose obvious. However, it does not explicitly differentiate from the sibling tool 'delete_request' (singular) or mention 'all', relying on the tool name to imply bulk deletion.

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?

It provides a clear use case: 'Use to reset an inbox before a new sign-up or test run.' This gives strong contextual guidance for when to invoke the tool, though it does not mention when not to use it or name alternatives.

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