get_realtime_price

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention the return format, potential delays, authentication requirements, or any errors. For a read-only price tool, this minimal description lacks transparency about what the agent should expect.

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 sentence that directly states the tool's purpose. It is front-loaded and contains no filler words.

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 tool is simple with one optional parameter and no output schema. However, the description does not explain what the tool returns (e.g., numeric price, object with price/currency). It does not address whether the price is in fiat or crypto, or any edge cases. Given the absence of an output schema, the description is incomplete for an agent to understand the resulting data.

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 has 0% description coverage, and the description only says 'in a specified currency' without naming the parameter or providing constraints. While the schema shows 'currency' with type string and default USD, the description does not clarify allowed values, format (e.g., ISO 4217), or that it is optional. It adds no meaning beyond what the schema already shows.

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 gets the current real-time Bitcoin price in a specified currency, using a specific verb (Get) and resource (current Bitcoin price). It is distinguishable from siblings like get_price_history (historical data) and convert_currency (currency conversion).

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 for real-time pricing through the word 'current', but does not explicitly state when to use this tool versus alternatives like get_price_history or get_supported_currencies. There is no exclusionary guidance or mention of contexts where this tool is not appropriate.

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