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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds material behavioral context the annotations do not: a per-call price ($0.002 USDC), the x402 payment rail (USDC on Base/Solana/Polygon/Arbitrum), and that x402 MCP clients auto-pay. It omits rate limits or failure/refund behavior, so it falls short of a 5.

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?

Purpose is front-loaded in the first sentence, followed by payment terms and a free-sample hint. The opening sentence is dense with a comma-heavy payload list, but each remaining sentence carries necessary information (pricing, payment mechanism, sample call), so there is little waste.

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?

There is no output schema, so the description correctly carries the return-value burden by enumerating balance, coins, staking/rewards, USD value, resolved name, and outgoing transactions. Combined with the payment disclosure and a runnable sample input, an agent has everything needed to call and interpret it.

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 100% and the single 'address' parameter is fully documented in the schema with both accepted forms. The description adds an example input address, which is marginally useful, but nothing about syntax or edge cases beyond what the schema already states, so the baseline 3 applies.

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 verb+resource ('Everything about an IOTA mainnet address or IOTA name') and enumerates the concrete payload: balance, all coins with symbols, staked IOTA per validator with estimated rewards, USD value, name resolution, and latest outgoing transactions. It is easy to distinguish from iota_network, but it does not explicitly differentiate itself from iota_tx or iota_watch, whose territory ('outgoing transactions', 'watch') partly overlaps.

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 'Everything about...' and the resolution note ('Resolves names to addresses and back'), so an agent can infer this is the general lookup tool. However, there is no explicit when-to-use vs. iota_tx/iota_watch guidance and no exclusions, leaving routing to inference.

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