redeliver_webhook

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, so the mutation/safety profile is partly covered. The description adds genuinely useful context beyond that: the side effect ('can trigger customer automation again') and the exact auth requirements (webhooks:write, owner/admin). It stops short of warning about duplicate/irreversible effects from non-idempotency.

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?

A single front-loaded sentence that leads with the action, then the consequence, then the permission prerequisite. No filler and every clause carries information.

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 non-idempotent write with an external side effect and no output schema, the description conveys the effect and auth needs but leaves both parameters unexplained and gives no hint of the response or failure behavior. Adequate but with clear gaps.

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 0% — both webhook_id and event_id are documented only by name and regex pattern. The description explains neither the identity of the webhook nor which event may be re-sent, so it fails to compensate for the coverage gap.

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 states a specific verb+resource: 'Send an existing event again to its configured endpoint'. It is clearly distinct from siblings like list_webhooks, list_webhook_deliveries, and retry_storage_delivery (a different domain). It does not explicitly name a sibling, but the action is 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?

It implies the use case (re-triggering a delivery) and gives a strong precondition via 'Requires webhooks:write and owner/admin', but never states when to choose this over alternatives or when not to use it. Guidance is implied rather than explicit.

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