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

With empty annotations, the description discloses critical behavioral details: the tool only transfers and does not activate ('does not activate or act on the transfer'), requires a PIN, has no Netfluid fee on internal transfers, converts received funds to customer credits, and optional linking to a subscription. It also explains the auto-search behavior for from_wallet_account_fk=0.

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 verbose and not tightly structured. The core purpose is mixed with promotional language ('implying a cost saving') and a somewhat rambling explanation of credits and optional linking. The @param section is necessary but could be better formatted. Some sentences could be combined or cut.

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 purpose, use cases, prerequisites (PIN), side effects (credits, optional linking), and return format. It lacks explicit failure/error information but is otherwise complete for a transfer tool, especially given the extensive parameter documentation.

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 has no property descriptions (0% coverage), but the @param block fully explains all five parameters, including special behavior for from_wallet_account_fk=0 (currency_fk=7 auto-find), amount decimal precision, and the return object. This fully compensates for the missing schema documentation.

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 primary action ('Transfers amount from wallet_fk, account_fk to the system wallet') and the context (account top-ups, logging payments). However, it doesn't explicitly distinguish from sibling transfer tools like netfluid__account_send or paywall__pay_subscription_with_wallet, so it is clear but lacks direct sibling differentiation.

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?

Provides explicit use cases ('Use it for account top-ups or if successful to log a customer payment') and mentions a cost-saving benefit. It doesn't specify when not to use or name alternatives, but the context is clear.

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