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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about ordering guarantees, how many runs are returned by default, whether results are paginated, or what 'FARM' means. It does at least hint at the returned record shape (status, parameters, queue time).

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?

It is short and front-loaded, but the terseness is under-specification rather than economy: an unexplained acronym ('FARM') and a bare comma-separated field list convey less than one clear sentence would.

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 the listed fields are largely redundant, and the description leaves the usage relationship to sibling listing/status tools and the purpose of 'limit' entirely unexplained. For a tool sitting among several similarly named listing tools, this is not enough to select and invoke it confidently.

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 the single 'limit' parameter, and the description never mentions it or explains its interaction with 'Latest'. An agent must infer from the schema name alone that limit caps the number of runs returned.

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 is essentially the tool name restated ('Latest runs:') followed by a field list. It conveys that runs are enumerated and newest-first, but there is no verb and nothing distinguishing it from siblings like backtest_status or list_strategies, which an agent could plausibly pick instead.

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 at all: no indication of when to call list_runs versus backtest_status, backtest_report, or list_strategies, and no prerequisites, exclusions, or pagination guidance beyond the bare word 'Latest'.

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