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

Beyond the annotations (which only confirm it is a write operation), the description provides vital behavioral context: it details exactly what the returned object contains (URL, reference, policies), the safety net that it 'never charges a card,' and an operational limit ('Rate-limited').

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?

The description is efficient and dense with necessary information, fitting the function into a single cohesive paragraph without unnecessary jargon. The most important information (no charge, rate-limited) is well-placed.

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 is a high-level payment creation tool, the description is highly complete. It explains the input purpose, the output structure (what data to extract), and the required external user interaction (sending the message).

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?

While the schema covers the inputs, the description effectively links these inputs (like size and work) to the final financial outcome and the specific data points returned, adding context about the end-to-end process.

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 and specifically states the purpose: to create a Stripe Checkout pay link. This distinguishes it immediately from sibling tools like 'get_work' or 'quote_order' by focusing on the creation of a payment mechanism.

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 provides clear instructions on how to use the resulting data, specifically directing the agent to send 'message_for_user' to the user in its reply. It also clarifies a critical functional constraint: 'This never charges a card.'

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