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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description goes substantially beyond them by disclosing the commercial model: $0.002 USDC per call, charged inside the call via x402, payment rails accepted (Base, Solana, Polygon, Arbitrum), automatic settlement for x402-aware clients, and a free sample via empty input. Cost and payment requirements are exactly the kind of behavioral trait annotations cannot express.

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?

The sentence is long but front-loads the highest-value information (what you get) before usage and pricing, and every clause earns its place since there is no output schema to carry the field list. It is dense but not padded.

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 carries the full burden of describing the return payload, and it does so field-by-field. Combined with the payment disclosure and usage context, an agent has everything needed to decide whether and how to call 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?

There are zero parameters and schema coverage is 100%, so the baseline is 4. The description reinforces this by noting the free sample is 'call with the example input {}', confirming no inputs are required, but there is no parameter meaning to add.

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 names the resource (IOTA mainnet) and enumerates the exact data returned: epoch, latest checkpoint, reference gas price, transfer fee, total/circulating supply, price and market cap, total stake, and every active validator with APY, commission and stake. That level of specificity makes it trivially distinguishable from the other iota_* siblings (iota_tx, iota_address, iota_watch), which operate on transactions/addresses rather than network state.

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?

It gives two explicit use cases — 'pick a validator' and 'show network health' — which is clearer than mere implied usage. It stops short of naming an alternative or an exclusion (e.g., pointing transaction lookups to iota_tx), so it earns a 4 rather than a 5.

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