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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It covers required scope, exact error pass-through behavior, live-config limits that change without deploy, the sender fee, and the 202 bridge block. It even warns against retrying with another destination, which goes beyond typical API documentation.

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 long but deliberately organized with capital-led sections such as WHO CAN SEND and LIMITS ARE LIVE CONFIG. Every sentence carries operational consequence, and the most critical constraints are front-loaded before the body schema. There is no filler or repetition.

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 high-complexity mutation with no annotations and no output schema, the description covers scope, eligibility, error behavior, dynamic limits, fees, response bridge block, and strict body typing. It points to external docs for verified-human caps and fee rates, which is appropriate. An agent has enough information to invoke the tool correctly.

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 compensates by enumerating the typed body: {from_wallet_id, to_wallet_id | to_handle, amount, platform?, note?, idempotency_key?, privacy_mode?, include_proof?, registration_id?}. It explains that registration_id is for quoted agent transfers and that any other field is refused. It does not fully define optional fields like privacy_mode or include_proof, but it clarifies the routing-critical parameters.

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 opens with 'Direct wallet-to-wallet transfer (POST /wallet/transfer)', giving a specific verb, resource, and endpoint. It clearly distinguishes this operation from the sibling tools by scoping it to direct wallet-to-wallet movement rather than proofs, quotes, or marketplace actions.

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 gives explicit when-to-use eligibility rules: verified human wallets may send to any wallet, while agent-class wallets may only send to registered destinations or their owner-of-record wallet. It also provides strong when-not guidance, such as 'Any other destination is refused 403' and 'do NOT retry with another destination.' It does not name alternative sibling tools, but the context is otherwise unambiguous.

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