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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds useful context that receivers deduplicate by event ID, but it does not explain the operational consequences of replaying events, rate limits, or whether replay can be undone.

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 with the core action, and no wasted wording. The deduplication note is brief and relevant.

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, open-world mutation with six parameters and no output schema, the description is quite terse. It covers the core action and receiver deduplication, but leaves out scoping, limits, and retry behavior that an agent may need before invoking it.

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%. The description clarifies that 'after' is a cursor and 'webhook' is the single target endpoint, but it says nothing about 'limit', 'company', 'environment', or 'idempotency_key', leaving several parameters to the schema alone.

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 and resource: queue past events after a cursor for redelivery to one endpoint. This is clearly distinct from sibling operations such as summer_webhooks_list and summer_webhooks_save.

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 explains what replay does but not when to use it, when to avoid it, or what alternatives exist. There is no guidance on prerequisites such as choosing a cursor or limiting replay scope.

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