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

Annotations already declare readOnly/openWorld/destructive=false, so the safety profile is covered. The description adds genuinely valuable behavior beyond them: a per-call price ($0.002 USDC), the exact payment rail (x402, USDC on Base/Solana/Polygon/Arbitrum), automatic settlement for x402 clients, and a free-sample escape hatch. It also scopes coverage to Sui mainnet. Rate limits and freshness/latency are not mentioned.

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-loads what the tool returns, then covers payment and the free sample. Two sentences on x402/automatic payment are somewhat redundant, but each element is actionable. No filler or marketing fluff beyond the pricing block.

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 compensates by enumerating the returned fields, which is the right move. Payment handling and a working example input are included. Only gap is no freshness/return-shape notes or validator-level detail limits, but for a one-parameter read tool this is close to 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 description coverage is 100% (the address parameter documents '0x + 64 hex or SuiNS name'), so the schema carries the burden and baseline is 3. The description adds a concrete SuiNS example ('alice.sui') and a full example address value, which aids invocation but is marginal beyond the schema.

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?

Names a specific resource (Sui mainnet address / SuiNS name) and enumerates exactly what it returns: SUI balance, all coins with symbols, staked SUI per validator with rewards, USD value, SuiNS name, and latest outgoing transactions. It is clearly a single-address aggregator, distinguishable in spirit from sui_watch or wallet_portfolio, though it never explicitly contrasts itself with those siblings.

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?

Usage is implied by the enumerated outputs rather than stated: an agent can infer it should call this to enrich one Sui address. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as sui_watch (monitoring), wallet_portfolio (multi-chain), or sui_tx (transaction detail). The x402 payment mechanics and free-sample call are useful how-to-call context, but not selection guidance.

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