BinanceTicker24hr

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

With no annotations, the description must carry the behavioral disclosure burden. It correctly implies a read-only operation via 'Get' and reveals the 'or all symbols' behavior, but it does not mention output shape, symbol formatting, response size implications, or potential errors. This is minimal but acceptable for a simple read-only tool.

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 concise sentence, front-loaded with the verb and object, and contains no filler or redundant information. It effectively communicates the tool's purpose in just nine words.

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 tool with one optional parameter and no output schema, the description provides sufficient context to select and invoke the tool: it states the purpose, scope, and the optional behavior. It does not list every returned statistics field, but that does not hinder initial use given the simplicity.

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 describes the single 'symbol' parameter with an example (BTCUSDT), and schema coverage is 100%. The description adds meaning by explicitly stating that the tool works for 'a symbol or all symbols,' which clarifies the optional parameter and the all-symbols case, adding value beyond 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 uses a specific verb and resource: 'Get 24-hour price change statistics,' which clearly identifies the tool's function and differentiates it from sibling ticker tools like BinanceTickerPrice or BinanceTickerTradingDay. It also includes the scope 'for a symbol or all symbols,' which is a distinguishing capability.

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 implies the tool is used when 24-hour price change statistics are needed, which provides basic context. However, it does not explicitly state when to avoid this tool or point to alternatives such as BinanceTickerPrice or BinanceTickerTradingDay, which is notable given the large set of sibling ticker tools.

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