BinanceTickerBookTicker

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

With no annotations, the description must carry the full burden. It implies a read-only operation via 'Get' and mentions the ability to fetch for all symbols, but it does not clarify whether both bid and ask sides are returned or describe the response structure. Some behavioral detail is present, but not comprehensive.

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?

A single, front-loaded sentence with no redundant words. The action and resource are immediately clear, and every word contributes to understanding the tool's purpose.

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 endpoint with one optional parameter and no output schema, the description covers the main purpose and scope. However, it omits explicit details about the return format (e.g., bid/ask quantities), which would help an agent fully understand what data to expect.

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 provides a complete description for the single 'symbol' parameter ('Symbol of the trading pair (e.g., BTCUSDT)'), achieving 100% coverage. The tool description adds no additional semantic meaning beyond what is already in the schema.

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 specific action ('Get') on a specific resource ('best price/quantity on the order book') with a clear scope ('for a symbol or all symbols'). It is informative enough to distinguish it from siblings like BinanceDepth or BinanceTickerPrice, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus other ticker/depth tools. The optional symbol parameter is noted, but there is no context on use cases, exclusions, or alternatives, leaving the agent to infer when this is the right choice.

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