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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: replay sits outside the monthly quota but inside a daily per-plan replay limit, quota-held events get billed as new, and non-idempotent receivers will double-process. This is exactly the kind of consequence disclosure a mutation tool needs.

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?

Three dense sentences, front-loaded with the action before the constraints, and no filler. The trailing clause about debugging is slightly conversational but still carries the idempotency warning.

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?

With annotations covering the safety profile and a fully documented schema, the remaining burden is behavioral, and the description covers quota, limits, billing, and duplicate delivery. It omits what happens when a replay is rejected by the daily limit or fails mid-delivery, which is a minor gap for a two-parameter tool with no output schema.

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 both parameters are already documented in the schema, including the quota note on 'id'. The description adds no syntax, format, or lookup guidance for the event ID, so the baseline 3 applies.

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?

States a concrete verb and resource: 'Re-send a stored event to its destinations.' An agent can tell this is a replay operation on a single stored event. It does not, however, differentiate itself from the sibling anyhook_replay_failed, which is the closest competing tool.

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 costs and side effects but never states the selection condition against alternatives — notably anyhook_replay_failed, which an agent could easily confuse with this tool. Usage is only implied by the scenario described ('replaying an event that was held for quota').

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