Reenviar link de pagamento por e-mail

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

Adds value beyond annotations by confirming no new creation occurs (non-destructive). Annotations already indicate non-destructive, but description reinforces the resend-only behavior, enhancing understanding.

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?

Two sentences, front-loaded with the action, no wasted words. Efficient and clear.

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?

Given the tool's simplicity and existence of an output schema, the description covers purpose, usage scenario, and limitations adequately. Could be more detailed about side effects, but sufficient.

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% for both parameters, so baseline is 3. Description does not add additional meaning beyond the schema's basic descriptions for 'email' and 'id'.

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 it resends an existing payment link email for a charge, using specific verbs and resource. It distinguishes from siblings like 'send_subscription_link_email' by specifying 'already created for a charge'.

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: when the payer did not receive or lost the original message. Also clarifies that no new link or charge is created, helping avoid misuse. Doesn't explicitly mention alternatives but provides clear context.

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