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

With no annotations, the description carries the full burden and discloses that data is read onchain, what supply and peg fields are returned, and that pricing is via x402. It does not cover auth mechanics, rate limits, or error behavior, but it is substantially more transparent than a bare read operation.

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 description is front-loaded with the use case and then compresses inputs, outputs, scope, and an example into a short block. It is dense and semicolon-heavy but has little wasted wording.

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 must explain return values, and it does: per-token and chain totalSupply, 24h/7d changes, per-symbol sums, USD net change, biggest movers, block numbers, and optional peg fields. For a three-optional-parameter read tool, this is complete enough to invoke correctly.

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 already 100%, so the baseline is 3. The description adds useful meaning by specifying allowed chain values (all, ethereum, base) and explaining that peg=true adds Chainlink price, deviation, and depeg status; the remaining symbol semantics are mostly left to 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?

States a specific action and resource: tracking stablecoin liquidity via mint/burn supply and peg data. It also names the supported chains and the exact output categories, so an agent can distinguish it from unrelated sibling tools such as stablecoin_freezes or proof_of_reserve.

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?

The opening sentence gives a clear use case: tracking stablecoin liquidity as a market signal. It adds the important scope exclusion 'Ethereum + Base only' but does not explicitly compare this tool with alternatives or state when not to use it.

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