binance_get_order_book

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

Even though annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, the description adds meaningful behavioral detail: weight tiers by limit, the hard 500 cap, Markdown top-50 truncation vs. full uncapped JSON, lastUpdateId inclusion, and Binance error code -1121 for invalid symbols.

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 organized into clear labeled sections: endpoint, weight tiers, when to use, when not to use, return format, example, and error handling. Every section adds practical value, and the core purpose 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?

For a read-only market-data lookup, the description covers endpoint, cost/limits, expected return shapes, an example call, and a likely error. Nothing material is missing for an agent to select and invoke the tool 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?

The schema already documents symbol, limit, and response_format, and the description reinforces this by explaining the limit cap and weight implications, providing a concrete symbol example, and detailing how response_format changes the returned data shape. This is more than enough to guide correct invocation.

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 current order book (bids/asks) for a symbol.' It also names the underlying endpoint and clearly distinguishes itself from related ticker and trade-history tools.

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?

There are explicit 'When to Use' and 'When NOT to Use' sections. The description names concrete alternatives like binance_get_book_ticker, binance_get_recent_trades, and binance_get_agg_trades, and explains why they should be chosen instead.

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