list_runs

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint). The description adds behavioral context beyond annotations by noting that pagination must preserve the original filters, which warns about a common misuse. No contradiction with annotations.

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 entire description is one sentence with two purposeful clauses. It front-loads the core purpose and adds a key pagination caveat without any filler or repetition.

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 description plus annotations and rich input/output schemas cover most safety and structural aspects. However, it lacks a clear statement of when to use list_runs versus get_run or other run-related tools, and does not mention that 'limit' controls page size or that 'filter' is optional. It is minimally viable but leaves some usage context implicit.

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?

The description provides almost no parameter-level detail. It mentions filters generically and refers to next_cursor, but does not explain the 'limit' parameter or the input 'cursor' parameter. With 0% schema description coverage and no property descriptions, the agent must infer semantics from the schema names alone, which for filter fields like lease_id may be opaque.

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 verb 'discover' combined with 'filtered run cohort' clearly indicates this is a list/search operation for runs with filtering. It is distinguishable from sibling tools like get_run, which targets a single run, though it doesn't explicitly name an alternative.

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 instruction 'follow next_cursor without changing filters' provides specific, actionable guidance on pagination, emphasizing that filters must remain constant during traversal. This gives clear usage context, though it doesn't explicitly state when to prefer this over other list or get tools.

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