account_deposit

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

Discloses behavioral traits: one on-chain settlement, non-refundable credits, off-chain debiting after deposit, no per-call 402/gas. Also mentions minimum deposit. Very detailed given no annotations.

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?

Description is dense but all information is relevant. Front-loaded with main action. Slightly long but efficient.

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?

Lacks description of return value or output format. No output schema provided. Describes usage well but omits post-call response details.

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?

Input schema has zero parameters; description adds context by explaining how to pass payment via meta. Baseline for 0 params is 4, and description compensates appropriately.

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?

Clearly states the tool opens or tops up a prepaid balance by depositing USDC on Base via x402. Distinguishes from sibling account_balance which likely reads balance.

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 clear context on when to use: to deposit USDC. Specifies minimum deposit and how to call with signed PaymentPayload. Does not explicitly state when not to use, but implications from siblings are clear.

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