Bulk-replay all failed events for an app

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

With no annotations provided, the description carries the full behavioral burden. It explains the action and intent, but does not disclose potential side effects such as duplicate downstream delivery, retry limits, rate limits, or whether the operation is reversible.

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?

Two short, purposeful sentences with no filler. The core behavior is front-loaded, and the second sentence adds practical context without redundancy.

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?

Minimally adequate for a tool with one required parameter and a clear scope. However, with no output schema and no annotations, an agent gets little guidance about expected return values, errors, or consequences of replaying all failed events.

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%, so the baseline applies. The description mentions the app slug but adds no meaning beyond the schema, which already documents api_key and appSlug clearly.

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 uses a specific verb 'Re-send' and defines the exact resource: 'every failed event for the given app slug.' The title's 'Bulk-replay' helps distinguish it from narrower siblings like anyhook_replay and anyhook_undelivered.

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?

Gives a concrete use case: 'useful after fixing a downstream bug to recover queued work.' It does not explicitly contrast with sibling tools, but the bulk scope makes the intended situation clear enough for an agent to select it.

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