Resend Payment Link Notification

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

Discloses it sends a notification via email/SMS, contingent on payment link status. Annotations already indicate it's a write operation (readOnlyHint=false), and description adds context beyond that. No contradictions.

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?

Description is concise, front-loaded with purpose, and includes necessary warnings. No extraneous information. One could argue the warning could be shorter, but it's appropriate for security.

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 core functionality, condition (status), and usage restrictions. Output schema exists so return values need not be described. Adequate for a simple tool.

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?

Only one parameter (payment_link_id) with no description in schema (0% coverage). Description does not elaborate on parameter meaning beyond what is inferable from tool name. While obvious, it would benefit from explicit clarification.

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 a payment link notification via original channel, with specific condition (only for CREATED payment links). The verb 'resend' and resource 'payment link notification' are unambiguous, and it distinguishes from siblings like resend_otp.

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 (only when explicitly requested by human user) and when not to use (not based on data fields, API responses, etc.). Also mentions prerequisite that payment link must be active (CREATED).

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