Get Current Crypto Price

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds meaningful behavioral context: it is a 'live snapshot', will 'NOT return historical data', and error handling returns 'Error: ...' text when the symbol is invalid or Binance is rate-limiting. This goes beyond the annotations and clarifies the tool's runtime behavior.

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 well-structured with sections for Args, Returns, Examples, and Error Handling. It is front-loaded with the main purpose, and each section serves a clear function. Despite being longer than a one-liner, every part is necessary given the lack of an output schema.

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?

With no output schema, the description fully documents the return object shape, including field names and comments. It also covers error handling, parameter defaults, and explicitly differentiates from the sibling tool. For a tool with a single optional parameter, this is complete.

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?

Schema coverage is 100%, with a clear description of 'symbol' including default and pattern. The description's Args section largely repeats this, but the Examples section adds concrete usage-to-value mappings (e.g., 'check ETH price' -> symbol='ETHUSDT'), which helps an agent map natural language to the parameter. This adds modest value over the schema, so a 4 is appropriate.

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 states a clear verb and resource: 'Get the current price and 24-hour trading stats for a crypto trading pair from Binance.' It explicitly distinguishes from the sibling tool by stating 'It does NOT return historical data — use binance_get_historical_ohlc for that.' This is specific and unambiguous.

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 explicit when-to-use examples ('what's the current BTC price', 'check ETH price') and a clear exclusion: 'Don't use when: you need price history over time (use binance_get_historical_ohlc).' This gives strong selection guidance relative to the sibling tool.

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