market_get_stablecoin_stats

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

Annotations already confirm a safe, read-only, idempotent operation. The description adds meaningful, non-redundant context by naming the external data source (DefiLlama) and detailing the exact return fields (name, symbol, supply, peg type, mechanism). It does not cover pagination or default chain behavior, but these are less critical given the strong annotation safety profile.

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?

Two concise sentences, front-loaded with the verb and resource, with no redundant or extraneous information. Every sentence contributes to understanding the tool's function and output.

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?

The description thoroughly covers the tool's purpose, data source, and return structure, while the schema handles the optional chain parameter. It could mention how the chain filter behaves when omitted, but given the tool's simplicity and strong annotations, it is nearly 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 schema documents the only parameter 'chain' with 'Filter by chain name', providing 100% coverage. The tool description adds no new information about this parameter, so it relies entirely on the schema's description.

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 uses a specific verb 'Retrieve' with a clearly defined resource 'stablecoin market statistics' and elaborates on the data included, such as circulating supply and peg data, plus the return structure. This makes it unambiguous and distinguishes it from other market tools like token price or DEX volume.

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 description provides clear context as a stablecoin-specific market statistics tool, implying when it should be used. However, it does not explicitly mention alternative tools or when not to use it, relying on the tool name and sibling list for differentiation.

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