transfer

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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context: idempotency_key prevents double charges and the memo is visible in the audit trail. However, it does not disclose other behaviors such as reversibility, fees, or failure handling, leaving some gaps.

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?

Three concise sentences, front-loaded with the core purpose. Every sentence contributes information (what it does, idempotency recommendation, memo option) with zero redundancy or filler.

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?

The description covers purpose and key parameter advice, but it lacks details on return values, failure modes, or prerequisites. Given the absence of an output schema and annotations, the tool would benefit from noting what the response contains or any required setup, making it only moderately complete.

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 coverage is 0%, so the description must explain parameters. It adds meaning for memo (reason, audit trail) and idempotency_key (prevents double charges), but provides no additional semantics for recipient or amount beyond the schema's names and 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 description clearly states the tool sends a standard Modexia payment (USDC) to a recipient, using a specific verb and resource. It distinguishes itself from sibling tools like cross_chain_transfer and nanopay by specifying 'standard' and the USDC currency.

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 implies when to use the tool (standard USDC payments) but does not explicitly mention alternatives or exclusion conditions. It provides usage advice for parameters (recommend idempotency_key, optional memo) but lacks guidance on when to choose this over cross_chain_transfer or nanopay.

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