list_runs

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

With no annotations, the description carries the burden and it does disclose non-obvious behavior: results are newest first, run.id is the UUID join key, and the integer runId column is deliberately not the join key. It does not cover pagination or auth, but an output schema is present for return shape.

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?

Three sentences, all information-bearing: core action, data-model caveat, and concrete use case. No filler and the key statement is front-loaded.

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?

The definition is strong for a default call and the output schema covers returns, but the undocumented 'car' filter and the lack of explicit limit semantics leave a clear gap. An agent can call it with defaults, but not fully understand optional filtering.

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% and the description does not explain either parameter. 'car' is completely opaque and 'limit' is only implicitly related to 'recent'; this is a significant gap for correct invocation.

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 first sentence states a specific operation and resource: 'List recent logging sessions (runs), newest first.' It defines the key entity and includes ordering, which is enough to distinguish list_runs from the query/export/browse siblings.

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 a concrete use case: resolve vague time references such as 'the last test' into a run id that export_series accepts directly. It does not, however, explicitly state when not to use this tool or name alternative list-like tools.

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