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

With no annotations, the description carries the full burden and does so thoroughly: link dies on completion, expires after ttl_s, card fee is added on top for the payer, funds stay in the Netfluid account until wallet_transfer, and the reference doubles as an idempotency key returning values.reused=1. It also discloses the security constraint that card details are entered on the hosted page only, never in chat.

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?

Content is front-loaded: what the tool returns, what to do with the link, then money semantics, then constraints, then parameters. It is dense but nearly every sentence carries decision-relevant information; the money paragraph is slightly run-on and could be split for scanability.

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?

For a 7-parameter financial write tool with no annotations, the description covers the return values even though an output schema exists (values.link, wallet_credit, card_charge_total, expires_at), plus fee model, idempotency, limits, KYC prerequisite, and the downstream wallet_transfer step. Nothing an agent needs to call this safely and correctly is missing.

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 description coverage is 0%, so the description must compensate, and it documents all seven parameters via @param tags with formats and defaults (PIN is 5 digits, description max 100 chars, ttl_s default 86400 clamped 300-86400, keep_card '1'/'0'). It also resolves the misleading schema default of ttl_s=0 by explaining the real default and clamping range.

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 first sentence gives a specific verb and resource: it returns a single-use hosted card-payment link for a customer's linked Netfluid wallet. It also distinguishes the mechanism ('hosted page where they pay by card (new card with 3D Secure)'), which separates it from sibling payment paths like payment_payat_link or wallet_visa_mastercard_recharge, though it never names those siblings explicitly.

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?

Strong operational guidance: hand values.link to the customer, never mint a second link for the same unpaid invoice, quote the exact price, amount must be 10-100000 ZAR, and the wallet must be KYC verified. It does not, however, explicitly route the agent to a sibling tool when the customer needs a different payment method (e.g. Payat, 3D Secure link, or card recharge).

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