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

Adds real context beyond the annotations: the replayed payload, signature, and X-Webhook-Delivery id are preserved, and the required `webhooks:write` API-key scope is named. It also warns that subscribers must be idempotent on duplicate delivery ids, which complements rather than contradicts the idempotentHint=false / destructiveHint=true annotations. It does not say whether the webhook must be enabled or what effect the replay has on delivery state.

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?

Front-loaded with the core action, followed by when-to-use, payload/signature semantics, and auth scope. Four sentences, all contributing; only minor redundancy between the 're-trigger downstream processing' and idempotency sentences.

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?

Covers action, motivation, payload identity, and permission scope for a mutation tool with no output schema. The main residual gap is the response shape — whether it returns a new delivery record or a status — but nothing critical for correct invocation is missing.

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 the required webhookIdentifier and deliveryIdentifier are already documented; the description only implies they select the 'specific past delivery'. No additional format or discovery guidance (e.g. obtain delivery ids from pm_list_webhook_deliveries) is offered, so 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 specific verb and resource: 'Re-send a specific past delivery to the webhook URL', which is clearly distinct from pm_test_webhook (synthetic test) and pm_list_webhook_deliveries (read). An agent can identify the operation without opening the schema.

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?

Gives concrete triggering conditions — subscriber was down during the original attempt window, or downstream processing must be re-triggered. It lacks explicit exclusions, e.g. that pm_test_webhook should be used for a synthetic payload or that deliveries must be located first via pm_list_webhook_deliveries.

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