Resend Transaction Webhook

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description does not explain what destructive means here (e.g., duplicate webhook delivery). It only mentions the 'completed' webhook type, adding minimal 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?

Single sentence with no extraneous information. It includes the endpoint and states the action concisely, making it appropriately sized and front-loaded.

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?

The tool has a destructiveHint and no output schema, yet the description fails to clarify consequences, success/failure behavior, or when it should be used. This incomplete context is risky for an action with potential side effects.

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 explain the transactionId parameter beyond showing it in the URL template. No additional semantics are provided; the schema already defines format and required status.

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 resends a transaction webhook and provides the specific endpoint path, distinguishing it from sibling tools like get_transaction or simulate_transaction. The verb 'resend' and resource 'webhook' are explicit.

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 information about when to use this tool, when not to, or alternatives. It lacks context about prerequisites (e.g., transaction must be completed) or situations where resending a webhook is appropriate.

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