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

Annotations are empty, so the description carries the full burden. It discloses several behavioral traits: Pay@ charges a minimum R12 fee deducted from funds received, funds remain in the Netfluid account until wallet_transfer, and both link and reference are valid for multiple uses. It also explains the account_fk=0 fallback behavior. This is substantive transparency, though it does not mention potential error conditions or idempotency of link creation.

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 longer than average, but each sentence earns its place by explaining the payment context, fee structure, parameter semantics, and return value. It is logically structured with clear @param and @return sections. Slight redundancy exists (e.g., 'Both the url and the payat_reference(_bw) code returned is valid for multiple use' could be merged with earlier sentence), but overall it is efficient given the complexity.

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 (payment link generation, South African context, fee deduction, multi-use codes, cross-border reference variants), the description covers all essential aspects: what it returns, how the payment flow works, fee implications, and parameter behavior. It also benefits from an output schema (not shown) which likely documents the return structure further. This is a complete and self-sufficient description.

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%, and the description fully compensates by documenting all three parameters: wallet_fk (Netfluid wallet_fk), pin (Netfluid wallet PIN), and account_fk (destination account, with 0 meaning auto-select first available ZAR account). It also clarifies the return object. This adds meaning well beyond the bare schema definitions.

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's purpose: 'Returns a Pay@ payment link and payat_reference for a Netfluid wallet.' This is a specific verb+resource construction that distinguishes it from sibling tools like paywall__payment_3d_secure_link and netfluid__fund_payat. It also explains what Pay@ offers (online and physical payment options), making the tool's scope unambiguous.

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?

The description provides clear usage context: it explains when to use Pay@ (for receiving payments via Netfluid wallet, both online and at physical till points) and details how the payment process works (customer chooses amount, unique reference, multi-use validity). However, it does not explicitly mention alternatives or exclusions, such as when to use a different payment method or sibling tool like netfluid__fund_payat instead.

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