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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond the annotations by disclosing that six tools are combined via Promise.all, and it lists what data is included. It does not, however, explain rate-limit impact or output shape/rounding.

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 two sentences with no filler: the first fronts the composite concept and lists the components, the second adds the longer-history alternative. Every part earns its place and it is easy to scan.

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 composite tool has moderately high complexity with six aggregated outputs and no output schema, yet the description does not explain the return shape/format at all. It conveys what is aggregated and when to choose an alternative, but an agent might not know how results are organized or what the 'overview' looks like.

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%, and the symbol parameter's description already includes the pattern, examples, and a requirement that the pair be a listed Binance USDS-M perpetual. The tool description adds no extra parameter semantics, so baseline 3 is appropriate.

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 this tool provides an overview of one pair in a single call and enumerates six concrete data components: funding/basis, 6h OI trend, 4h top-trader, 4h taker volume, order book, and 24-candle 1h price bias. It also distinguishes itself from individual sibling tools by explicitly naming the composite Promise.all aggregation.

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 explicitly says for longer history, use the individual tools (e.g., binance_get_open_interest_history), which is a clear when-not and alternative-to guidance. The composite purpose is also evident: quick multi-signal overview in one call.

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