BinanceTicker

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly conveys that this is a read-only operation ('Get') and adds useful context about the rolling window nature and the ability to query all symbols. It does not discuss rate limits or error behavior, but for a simple read-only ticker endpoint, the description is sufficiently transparent.

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, front-loaded sentence that communicates the essential behavior without any wasted words. It is grammatically clear and easily parsed by an agent.

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 tool with only two optional parameters and no output schema, the description is nearly complete: it states the resource type, the time window, and the symbol scope. Minor gaps include not specifying the exact return fields (e.g., that it returns detailed statistics like lastPrice, priceChangePercent) and not clarifying the default windowSize behavior beyond '24-hour', but these are not critical given the schema descriptions.

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 provides 100% coverage for both parameters, so the baseline is 3. The description adds no additional meaning beyond what the schema already states, except implicitly confirming that the 'symbol' parameter can be omitted to return all symbols. This matches the schema's optionality but does not go further.

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 clearly states a specific verb ('Get') and resource ('24-hour rolling window price change statistics') with optional symbol scope. It is specific and actionable, but does not explicitly distinguish itself from closely related sibling tools like BinanceTicker24hr or BinanceTickerTradingDay, which likely share a similar purpose.

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 usage when 24-hour price change statistics are needed, and notes that it can be called for a single symbol or all symbols. However, it offers no explicit guidance on when to use this tool versus the many related ticker endpoints (e.g., BinanceTicker24hr, BinanceTickerPrice, BinanceTickerBookTicker), and provides no exclusions or alternative recommendations.

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