binance_spot_price

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

With no annotations, the description carries the full burden. It discloses real-time updates, millisecond fluctuations, the 100-pair batch limit, and that prices are reference-only. It also adds data source and latency details ('Binance 官方 API', '< 100ms'), providing useful behavioral context.

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 clear sections, but it is verbose. Decorative emojis and a redundant '交易提示' block add length without enhancing understanding. The output example is useful but could be trimmed.

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 single-optional-parameter tool with no annotations or output schema, the description covers use cases, behavioral warnings, limits, and an illustrative output. Missing details about multi-pair input format are the main gap, but overall it is sufficiently complete for an agent to invoke the tool.

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% for the single symbol parameter, so the baseline is 3. The description adds a generic '支持单个查询或批量查询' but does not clarify how batch input should be formatted (e.g., comma-separated list), which is a gap since the schema only shows single-pair 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 explicitly states '获取现货市场的实时价格信息' (get real-time spot market price information), clearly identifying the verb and resource. It distinguishes from siblings like binance_futures_price by specifying '现货' (spot) and from orderbook/ticker tools by focusing on price.

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 '适用场景' section provides clear use cases (market monitoring, pre-trade reference, portfolio valuation) and the '重要提醒' warns about batch limits and price volatility. However, it does not explicitly name alternative sibling tools or state when NOT to use this tool.

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