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

Annotations are empty, so the description carries the full burden. It does disclose useful behavior beyond a bare verb: the geo/currency restriction and the notable fact that it returns bank details rather than pushing money, implying a deposit-instruction flow. It stops short of saying whether the account is credited immediately, what auth/KYC state is required, or what happens on expiry of the returned details.

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 core facts are front-loaded and the @param tags are easy to scan, but the opening sentence and the second sentence say the same thing twice, and '@return: a json object' is pure filler. Roughly a third of the text is redundant.

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 three-parameter funding tool with no annotations and no output schema, the parameter documentation is adequate, but the return is described only as 'a json object' even though the description elsewhere claims it returns bank details. An agent still lacks the shape of the returned details and any follow-up step needed to complete the payment.

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 does: it documents all three parameters, gives token provenance (/access/login), and crucially clarifies that account_fk is a database integer ID rather than an account address and may not be 0, sourced from /wallet/accounts_list. That is meaningful semantics an agent could not infer from the bare types.

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 opening states a specific verb and resource ('Funds an account with a PayShap payment') and identifies the payment rail, which distinguishes it from siblings such as fund_payat, fund_card_recharge and fund_ott. It loses a point for restating the same action a second time without adding scope or 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?

It gives real eligibility constraints ('only available in South Africa', 'can only be redeemed against a ZAR currency account'), which implies when the tool is valid. However it never compares itself to the other funding siblings (fund_payat, fund_banks, account_buy) or states when a different rail should be chosen instead.

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