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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds genuinely non-obvious behavior: a free quota of 10 calls/day, $0.001/call thereafter, the payment channel (params._meta["x402/payment"], HTTP, or X-API-Key credits), and the upstream data source and license. It stops short of saying what a caller sees when the quota is exhausted or payment is absent, but the rate-limit and auth disclosure is well beyond the annotation baseline.

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 returned payload, then source, then access/pricing — a sensible order with no filler sentences. The bracketed '[served by tools.moneytools.dev]' and the payment-channel detail are somewhat dense, but each sentence carries operational information.

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?

For a single-parameter read tool with a full output schema, annotations, and 100% schema coverage, the definition supplies the source, licensing, and access-cost model an agent needs to decide whether to spend a call. The one remaining gap is error behavior for unknown chain ids or quota exhaustion, which is minor given the output schema carries the return shape.

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 schema already says 'numeric chain id or common name' with an example. The description restates the chain-id input in its arrow notation but adds no format, naming convention, or failure behavior for unrecognized ids, so the baseline of 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?

The arrow notation 'Chain id → name, native currency, public RPCs, explorers, CAIP-2 id and a ready wallet_addEthereumChain object' names the input key and enumerates exactly what comes back, which makes this a chain-registry metadata lookup and clearly not erc20_info or address_profile. An agent can select it without opening the schema.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative; the description never says e.g. 'use erc20_info for token metadata' or 'prefer this over contract_abi for RPC endpoints'. Usage is only inferable from the stated payload, and the pricing/auth sentences describe cost mechanics rather than selection criteria.

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