get_supply_info

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

No annotations are provided, so the description carries full burden. It discloses what data is returned (behavioral output), which is valuable context. However, it does not explicitly state this is read-only, mention rate limits, authentication requirements, or data freshness guarantees. The 'Get' verb implies safety, but explicit behavioral traits are missing.

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?

Single sentence structure with the action and resource front-loaded ('Get Bitcoin supply data'), followed by a colon-delimited list of specific metrics. Zero redundant words; every element earns its place by specifying scope.

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 parameterless read operation with an output schema (per context signals), the description is complete. It lists the specific data fields returned, which is sufficient given the low complexity and absence of input parameters requiring documentation.

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 input schema contains zero parameters. Per scoring rules, zero-parameter tools receive a baseline score of 4. The description appropriately requires no parameter explanation.

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 ('Get') and resource ('Bitcoin supply data'), then enumerates exact data points returned (circulating supply, max supply, inflation rate, subsidy per block, next halving estimate). This distinguishes it from sibling tool 'get_halving_countdown' by positioning this as comprehensive supply metrics versus countdown-specific data.

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 implies usage through the listed data points (use when you need these specific supply metrics), but provides no explicit when-to-use guidance or comparison to alternatives like 'get_halving_countdown', which also covers halving information. No prerequisites or exclusions are mentioned.

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