create_topup_link

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

Beyond annotations, the description discloses that it creates a pending Stripe session without charging, requires human to open URL in browser, agent cannot complete payment, and balance updates only after checkout completes. This is consistent with annotations (readOnlyHint=false, openWorldHint=true) and adds critical behavioral context.

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 somewhat lengthy but each sentence adds value. It is well-structured with purpose first, then usage, side effects, and disambiguation. Could be slightly more concise but remains effective.

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 complexity and the presence of an output schema (not shown but indicated), the description covers all essential aspects: purpose, when to use, side effects, human-in-the-loop requirement, and integration workflow for test/live modes.

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 the single parameter amount_cents. The schema description already includes min/max, example, and unit. The tool description repeats this information without adding new meaning, so baseline 3 is appropriate.

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 generates a one-time Stripe Checkout URL for adding funds to prepaid balance. It specifies the verb 'Generate' and resource 'Stripe Checkout URL', and distinguishes from siblings by noting it only mints a payment link and never moves money or blocks.

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 get_balance shows insufficient funds for submit_query or a human asks to add money. Provides disambiguation about what it doesn't do (no money movement, blocking) and includes notes on test-mode vs live-mode.

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