get_circulating_supply

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

With no annotations, the description bears full responsibility for behavioral disclosure. It does convey that the output is a single number and that the data is 'raw', which provides some insight. However, it does not mention whether the value is live, cached, or subject to updates, nor does it clarify any potential rounding or formatting behaviors.

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 a single succinct phrase that wastes no words and immediately conveys the core purpose. It is appropriately terse for a tool with no parameters and a simple output. Every word in the phrase contributes meaningful 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?

The description is too sparse for the context of a tool family with overlapping names (get_usdd_supply, get_total_supply, get_susdd_supply). It does not explain what makes 'circulating supply' distinct from these alternatives, nor does it provide any context about the data source or usage scenario. This incompleteness could lead an agent to select the wrong tool.

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 the input schema is empty. The description correctly omits parameter details, and no additional semantic explanation is needed. The baseline score of 4 applies for no-parameter tools.

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 as 'USDD circulating supply' and implies a retrieval operation despite missing an explicit verb. It distinguishes from total supply concepts through the word 'circulating', though it doesn't explicitly reference sibling tools. The phrase 'single number' adds clarity about the expected output.

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 guidance on when to use this tool versus closely related siblings like get_usdd_supply or get_total_supply. The description does not explain the distinction between circulating and total supply or state any prerequisites. An agent would have to infer the appropriate context from the tool name alone.

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