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

No annotations exist, so the description carries the full burden. It discloses ordering (newest first), the optional strategy filter, and payment/auth requirements. However, it does not describe the shape of returned backtest entries or any pagination behavior beyond the limit parameter, leaving some behavioral gaps.

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 front-loaded with purpose and usage, but it repeats 'newest first' twice (once in the opening phrase and again in 'Results are newest first'). That redundancy and the bracketed payment note slightly dilute conciseness, though nothing is egregiously verbose.

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?

With no output schema and no annotations, the description needs to be self-sufficient. It covers purpose, filtering, ordering, the alternative tool, and access/payment requirements. It leaves the exact return fields undefined, which is a gap for a list tool, but the core information an agent needs to invoke it correctly is present.

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%, so the baseline is 3. The description adds value by explaining that strategy_id optionally restricts results to one strategy's runs and that results are ordered newest first. It does not add syntax details beyond the schema, so it remains slightly above baseline.

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 ('recent backtest runs, newest first') and explicitly names the sibling get_backtest for fetching a single result. An agent can distinguish it from list_strategies, run_backtest, and get_backtest without opening any schema.

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?

Names the triggering user intents ('what they have run', 'refer to an earlier result without giving an id'), the alternative tool to use next (get_backtest), and the behavioral benefit ('avoid re-running'). No significant ambiguity remains about when to choose this over siblings.

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