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

The description reconciles the unusual annotation combination (readOnlyHint=false with idempotentHint=true) by explaining that the address is 'created on the first call, then the same' — exactly the write-once-then-stable behavior an agent needs to know. It also adds 'Free' (no cost) and the crediting rule (1:1) that annotations cannot convey.

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?

Front-loaded with the resource, then the operational detail, then the terse 'Free.' payoff. No sentence is filler; the parentheticals carry real information (first-call creation, transfer method per chain) rather than restating the name.

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?

With no output schema, the description does explain what comes back (a per-account USDC address) and the downstream effect of using it. It stops short of stating auth/precondition requirements or pointing to get_deposits/get_ledger to confirm credit, which would close the loop for a funding workflow.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The adjacent semantic content it does supply — supported chains and the usdSend vs ERC-20 transfer distinction — is useful context even though it is not tied to an input field.

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?

States a specific resource ('Your USDC deposit address') and what it is for: sending USDC on HyperCore, HyperEVM, Base or Arbitrum One, credited 1:1 to balance. An agent immediately knows this retrieves a funding address rather than deposit history (get_deposits) or payment quotes (quote_wallet_payment).

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?

Clear context for when to call it — the agent needs a funding destination or an explanation of how to pay on each chain. It does not name alternatives or exclusions (e.g., 'for deposit history use get_deposits', or 'for card/bank funding use get_payment_options'), so routing is inferred rather than stated.

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