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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that execution is paper-only, that the window is fixed at the last 7 days, and that capital is fixed at $10,000 rather than parameterized — but it says nothing about determinism, runtime, or what the simulation returns.

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 wasted preamble; the verb and core assumptions land immediately. The closing clause about the 'OUROS launch desk' engine is credibility framing rather than actionable information, which keeps it just short of a 5.

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 an 11-parameter simulation tool with no output schema, the description should say what a backtest yields (equity curve, PnL, trade list) and whether results are reproducible. It also leaves the 7-day window and fixed $10,000 capital potentially in tension with perDay/perTrade parameters, without clarifying how the caps interact.

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 73%, above the midpoint, so the schema carries most of the load and a 3 baseline is appropriate. However, the description adds zero parameter-level meaning and does not compensate for the three undescribed enum parameters (lookbackH, rebalanceH, maxLeverage), nor does it explain how 'type' interacts with 'long'/'short'.

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 ('Paper-backtest a pair strategy') plus the data source (Hyperliquid prices) and fixed notional ($10,000), which no sibling tool offers. It is clearly distinguishable from get_markets, get_signals, and get_model_prices, though it never names those alternatives explicitly.

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 gives no when-to-use or when-not-to-use guidance and does not point to any sibling tool for alternative workflows. 'Paper-backtest' implies a simulation rather than live execution, but that is the only usage signal and it is left implicit.

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