list_test_runs

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful extra that results come back newest-first, but leaves unexplained how many 'recent' sessions are returned and whether there is an implicit cap — relevant because there is no paging parameter.

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 short sentence with the ordering and filter front-loaded and no wasted clauses. The only weakness is that 'Recent' is left undefined, making the sentence underspecified rather than 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?

An output schema exists, so return shape needn't be explained. For a single-optional-param list tool the essentials are present, but the undefined result window ('recent') matters because the schema offers no limit/offset control, leaving the agent unable to predict result volume.

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 100%, so the single optional 'state' parameter is already fully documented including its enum. The description's 'optionally filtered by state' adds the fact that omitting it returns all states, plus the newest-first ordering, which is a small but real increment over the schema.

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 pair implicitly: lists 'test sessions' with a stated ordering ('newest first') and an optional state filter. An agent can distinguish it from siblings like test_status or test_start by the plural collection noun, though the description never names those siblings 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?

'Optionally filtered by state' implies the browsing/history use case, but the description gives no explicit when-to-use versus alternatives such as test_status (current run) or list_evidence, and no statement of when not to use it.

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