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

Description goes well beyond the annotations, disclosing that it terminates in-flight deliveries, invalidates existing webhook payload records, and regenerates/resends them. It also adds the rate-limit detail. Nothing contradicts the destructiveHint=true or idempotentHint=false 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?

Three sentences with no filler: main action, use case, then critical warnings. The destructive behavior and rate limit are front-loaded in the same compact block, making the tool's risk profile immediately visible.

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, non-idempotent tool, the description discloses side effects, rate limiting, and appropriate invocation context. An output schema exists, so return-value documentation is not required here. The description is complete enough for an agent to call it safely with the provided 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%, with both searchBy and trackerId already documented inline. The description adds no new parameter-level detail beyond referring to 'a tracker,' so the baseline of 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?

Description opens with a specific verb+resource: 'Replays all webhook events for a tracker.' It clearly separates this from siblings like download_webhook_history by focusing on replay/resend rather than retrieval. The use case 'when your endpoint missed or failed to process previous notifications' further pins down the purpose.

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?

Explicitly states when to use: 'Use when your endpoint missed or failed to process previous notifications.' It also gives a clear when-not: 'do not call repeatedly in quick succession,' plus a rate-limit constraint. While it does not name an alternative sibling, the stated context is sufficient for an agent to decide.

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