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

With no annotations, the description must disclose behavioral aspects. It mentions the cost ($0.005 USDC per call) and the data fields returned, but omits details like rate limits, error handling, or whether it is strictly read-only (though that is evident). There is no mention of output format, pagination, or handling of invalid symbols, leaving significant gaps for a tool with zero annotation coverage.

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 efficiently conveys purpose, data fields, examples, and cost. It front-loads the core function and includes a price indicator, making it highly concise and well-structured.

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 one-parameter tool with no output schema, the description covers the essential data fields and examples. It lacks explicit mention of error scenarios or symbol format constraints, but these are minor for a ticker service. The cost disclosure adds practical context. Overall, it is nearly complete for an agent to use correctly.

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 0%, so the description is the only source of parameter meaning. It provides example symbols (BTCUSDT, ETHUSDT) implying the 'symbol' parameter format, and indicates more are supported. However, it does not explicitly state that the parameter is optional (default BTCUSDT) or clarify uppercase/lowercase requirements, relying on inference from examples.

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 retrieves crypto tickers from Bybit spot market, listing specific data fields (price, 24h change, volumes) and example symbols (BTCUSDT, ETHUSDT). This distinguishes it from sibling tools like moex_quote (stocks) and cbr_rates (currency) by specifying the exchange and asset class.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. However, the Bybit crypto context strongly implies it is for cryptocurrency quotes, which is a clear use case. No direct comparison to other tools is provided, so guidance is implicit rather than explicit.

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