binance_get_ticker_price

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

Annotations already mark this as read-only, idempotent, and non-destructive, but the description adds significant behavioral context: API weight costs per symbol, the 100-row Markdown cap, JSON `count`/`shown` fields, and the `-1121 Invalid symbol` error. This is exactly the kind of information annotations do not convey.

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?

Well-structured with clear sections: purpose, endpoint/weight, when to use, when not to use, returns, examples, and errors. Each sentence adds value, and the most important distinguishing fact (least overhead ticker) is front-loaded.

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 description, combined with the schema and output schema, covers everything an agent needs: what the tool returns, how to request single/multiple/all symbols, cost/weight implications, alternative tools, and error behavior. No meaningful gap remains for a tool of this complexity.

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 context signal reports 0% schema description coverage, so the description must compensate. It does so with concrete examples for `symbol` and `symbols`, notes that omitting both fetches all prices, and explains the effect of `response_format` via the Markdown/JSON Returns section. It slightly overlaps with schema text about mutual exclusivity but adds practical usage 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 opens with a specific verb and resource: 'Fetch the latest price for one, several, or all symbols.' It names the exact endpoint and differentiates from sibling ticker tools by contrasting with `binance_get_book_ticker` and `binance_get_ticker_24h`, so an agent can select it confidently.

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?

Contains explicit 'When to Use' and 'When NOT to Use' sections, naming the exact alternative tools for bid/ask spread and 24h stats. This gives unambiguous routing guidance beyond any inference needed from the schema.

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