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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so safety framing is partly covered. The description adds one genuinely useful trait ('Receivers deduplicate by event ID'), but omits what gets re-delivered/overwritten, permission needs, and rate limits. With annotations carrying the safety profile, this is an average add.

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 sentences, front-loaded and free of padding. The first sentence, however, restates the title almost verbatim, which is mildly redundant rather than additive.

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 6-parameter, destructive, non-idempotent mutation tool with 50% schema coverage and no output schema, two sentences is thin. It never states what the call returns, what the cursor references, or how much is re-queued by default, leaving the agent under-informed for a side-effecting operation.

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 50% (after, limit, and webhook are undocumented in the schema). The description adds meaning to 'after' (cursor semantics) and implies the endpoint maps to the webhook parameter, but gives no explanation of limit or the event-ID format expected in 'after', so it only partially compensates.

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 states a specific verb ('Queue ... for delivery again') and resource ('past events after a cursor') with a scoping detail ('to one endpoint'). It is clearly distinguishable from list/save siblings, but it never names or contrasts those siblings, which is what a 5 would require.

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?

There is no explicit guidance on when to use this tool versus alternatives, no preconditions, and no warning about when replaying is inappropriate. The dedup note is behavioral context, not usage guidance, so this sits at 'no guidance'.

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