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

No annotations are provided, so the description carries the full burden. It discloses the output content (supply, per-coin, chain distribution) but does not describe response format, update frequency, historical depth, or any limitations. For a data-retrieval tool, this leaves ambiguity about whether the result is a snapshot, time series, or list.

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 two sentences, front-loaded with the core purpose ('Stablecoin supply tracking') and then details the key fields. Every word adds value; no fluff or redundant phrasing.

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?

Given no output schema and no parameters, the description lists the primary data categories but lacks specifics such as which coins/chains are included or whether the data is current/historical. It is adequate for a simple tool but not fully 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?

The tool has zero parameters and an empty schema, so there is no parameter ambiguity to clarify. Per the baseline for zero-parameter tools, the description does not need to add parameter details; it sufficiently conveys the expected data scope.

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 clearly identifies the resource ('stablecoin supply') and lists the specific data dimensions provided (total supply, per-coin breakdown, chain distribution). While the verb 'tracking' is not an imperative like 'get' or 'list', the scope is unambiguous and distinguishes it from sibling flow-focused tools like chain_flows and protocol_flows.

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 phrase 'leading market indicator' implies a market-analysis context, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives. The description does not contrast with sibling tools or explain when stablecoin supply data should be used over flow data.

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