get_usdd_supply

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the supply is per-chain and excludes sUSDD, which adds context beyond the tool name. However, it does not mention output format, data source, or any limitations, leaving some ambiguity about what exactly will be returned.

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 action and scope, and contains no unnecessary information. Every word contributes to understanding the tool's purpose and usage.

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 simple getter with no parameters and no output schema, the description sufficiently conveys what the tool does and when to use it. While it might benefit from clarifying which chains are included or the exact return structure, the essentials are covered.

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, so the schema trivially covers 100% of parameter documentation. Per rubric, a baseline of 4 applies when no parameters exist, and the description adds no parameter semantics because none are needed.

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 states the tool's function: 'USDD supply broken down by chain, excluding sUSDD.' It uses a specific verb and resource, and distinguishes from sibling tools like get_susdd_supply by explicitly excluding sUSDD and highlighting per-chain distribution.

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 a clear use case: 'Call this MCP tool for per-chain USDD distribution.' It also excludes sUSDD, implying a boundary against using it for sUSDD data. However, it does not explicitly name alternative sibling tools, so it misses the 'when not to use' guidance at the highest level.

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