binance_get_trading_day_ticker

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description discloses request weight, a weight cap for large symbol counts, the 100-symbol limit, markdown/JSON return behavior, and local validation errors. This is substantial behavioral context that annotations alone do not provide.

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 headers, front-loaded purpose, and each section (endpoint, usage, returns, example, errors) earning its place. It is detailed yet skimmable for 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?

The description covers the endpoint, rate limiting, symbol limits, response formats, example input, and error conditions. Given the schema and annotations, nothing critical is missing for correct invocation and interpretation.

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?

Although the nested schema already documents each field, the description adds a practical example with time_zone, clarifies the max 100 symbols constraint, and explains local rejection logic. This meaningfully supplements the schema without repeating every parameter.

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 price change statistics for the current trading day (a fixed calendar window).' It also names the exact endpoint, GET /api/v3/ticker/tradingDay, and explicitly distinguishes the calendar-day semantics from the rolling 24h sibling, making selection unambiguous.

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 'When to Use' section gives a concrete condition (today's stats aligned to a timezone's midnight) and the 'When NOT to Use' section names the alternative tool, binance_get_ticker_24h, for rolling windows. This is explicit routing guidance with no ambiguity.

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