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

With no annotations, the description carries the full disclosure burden. It usefully names the outputs (trade count, win rate, cumulative PnL, max drawdown), implying a read/compute operation, but it says nothing about cost/latency of replaying history, permission needs, or whether the run has any side effects.

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?

A single front-loaded sentence with no filler; the action comes first and the return payload second. Nothing is wasted.

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?

There is no output schema, but the description compensates by listing the returned metrics. Gaps remain around what 'pages' controls, how much history is covered, and how the backtest relates to the live signal tools.

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 description coverage is 0% for 3 parameters. 'for one symbol' loosely maps to the symbol param and 'over history' hints at depth, but the 'pages' parameter (1-4) is never explained and the interval param's role is left entirely to its enum. The enums on symbol and interval do much of the work, keeping this at a baseline 3 rather than lower.

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?

States a specific verb and resource: 'Replay the position state machine over history for one symbol', and enumerates the returned metrics. This is clearly distinct from siblings like get_signal/get_signals, though it never names them explicitly to reinforce the difference.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_signal. The agent must infer that this is the historical-evaluation counterpart to the live signal tools.

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