Resend Webhook

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

Goes well beyond the annotations by disclosing the key behavioral nuance: a fresh attempt reusing the ORIGINAL event id, so consumers deduping on X-Porkbun-Webhook-Id will treat it as the same event. It also states the endpoint must exist and be ACTIVE. Annotations cover safety profile (non-read-only, non-destructive, non-idempotent) but not this dedupe semantics, which is exactly the extra value the description should supply.

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?

Four tight sentences, front-loaded with the action, then mechanism, then precondition, then usage. Every sentence earns its place with no restatement of the name or annotations.

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, side effects, dedupe behavior, and preconditions for a single-parameter mutation with no output schema. The only omission is what the call returns (new attempt id vs original) and any rate-limit or failure behavior, which leaves a minor gap.

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 100% and the single 'id' parameter already documents its origin ('from list_webhook_deliveries'). The description adds no format, range, or sourcing detail beyond the schema, so the baseline of 3 applies when structured fields do the work.

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-queue a past webhook delivery to its endpoint') and immediately clarifies the mechanism ('Clones the delivery into a fresh attempt'). An agent can distinguish it from test_webhook, sandbox_trigger_webhook, and get_webhook_delivery without inspecting schemas.

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 names the triggering scenario ('Use after fixing a downstream bug to replay a delivery that previously FAILED') and states a hard precondition ('The endpoint must still exist and be ACTIVE'). It does not name an alternative tool for cases where the endpoint no longer exists or is inactive, so it falls short of full alternative routing.

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