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

Annotations indicate not read-only, not idempotent, not destructive. Description adds 'queueing a replay' but does not explain if the operation is asynchronous, if multiple calls cause multiple replays, or if there are any side effects. The agent gets minimal behavioral context beyond the annotations.

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 a single 8-word sentence, very concise. However, it omits crucial information about parameters and usage, making it too terse to be fully useful. Every word earns its place, but the description lacks substance.

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?

Given one parameter and no output schema, the description should cover behavior, return values, and error conditions. It only states the purpose and authentication. Sibling tools like 'cancel_queued_retries' suggest related operations, but the description does not mention them. For a mutation tool, completeness is insufficient.

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 coverage is 0% and the description does not mention the 'eventId' parameter. The agent must infer that eventId is required and expects a string, but has no guidance on format, source, or validation rules (e.g., UUID format). This is a critical gap for correct invocation.

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 tool queues a replay of a single received event. It specifies 'authenticated' and distinguishes from sibling 'replay_events' (plural) and 'replay_message' (different entity), making the purpose specific and unambiguous.

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?

No guidance on when to use this tool vs alternatives like 'replay_events' or 'replay_message'. Does not mention prerequisites (e.g., event existence) or whether it should be used for individual event reparsing. The description only says 'authenticated', implying authentication is needed but not when to choose it over siblings.

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