Bitcoin price

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 core behavior—fetching current prices—and lists the currencies, but does not mention return format, update frequency, or potential network dependencies. This is moderately transparent for a simple read-only tool, but not comprehensive.

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?

A single, well-structured sentence front-loads the action and resource, and the currency list is concise and pertinent. No filler words or redundant information; every element earns its place.

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 zero-parameter price lookup tool, the description is largely complete: it names the exact data returned and the currencies. The lack of an output schema or return format description is a minor gap, but the tool's simplicity and the enumerated currencies make the output predictable.

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 schema coverage is 100% (trivially). The description adds semantic value by specifying which currency prices are returned, which is effectively the parameter space. With no params to document, the description adequately conveys the tool's inputs.

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 with a specific verb 'Get' and resource 'current Bitcoin price', and enumerates the supported currencies. This distinguishes it from sibling tools like get_recommended_fees or get_transaction, which cover different blockchain data areas.

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 when to use this tool: whenever a current Bitcoin price is needed. It provides a clear context without explicitly mentioning alternatives, but the simple, specialized scope makes the usage obvious. No exclusions or alternative tool references are provided, but they are unnecessary given the tool's specificity.

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