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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the trailing 'Read-only' adds little. The genuinely useful disclosure is that cells below the minimum sample are flagged, which tells the agent to expect sparse/low-confidence results; beyond that, nothing about data freshness or failure modes is added.

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?

One dense sentence front-loads the resource and metric list, and the trailing 'Read-only' is short. The only waste is the redundant read-only restatement of the annotation, but the whole description is proportionate to the tool.

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?

An output schema exists, so return-value details are correctly omitted, and the description still previews the metrics and the minimum-sample flagging. For a single-parameter read tool this is nearly complete, missing only a pointer to sibling tools for verdict/ranking context.

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 single parameter's description already lists the accepted symbol formats ('BTC, BTCUSDT, BTC-USDT-SWAP'). The description repeats those exact examples without adding format rules, normalization behavior, or case sensitivity, so it earns only the baseline 3.

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 gives a specific verb ('Get'), a specific resource ('per-strategy backtest statistics'), and enumerates the metrics returned (trades, win rate, profit factor, total return, exit reasons, data window), scoped to one coin. It is clear what the tool does, though it never distinguishes itself from the potentially overlapping sibling get_strategy_verdict.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The inclusion of example symbols implies how to call it, but not when to prefer it over siblings like get_strategy_verdict or get_strategy_verdict/list_strategies.

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