list_runs

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

No annotations provided. The description does not clarify what 'recent' means (e.g., time range, sorting order), nor does it mention pagination or behavior when limit is not specified. Behavioral traits beyond listing are not disclosed.

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 very concise with one sentence, but it lacks structure and could include parameter details without significant bloat. It is not verbose but misses opportunities to be more informative.

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?

Given the tool has a nested object parameter, no output schema, and no annotations, the description is too minimal. It fails to explain optionality of the target, the meaning of 'recent', or what the response contains.

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%. The description adds no meaning beyond the parameter names; it does not explain the purpose of limit or the nested target object's fields.

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 clearly identifies the tool as listing recent runs for a flow target, but it does not differentiate from sibling tools like get_latest_run or get_run, which would benefit from explicit contrast.

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?

No guidance on when to use this tool over alternatives such as get_run (single run) or get_latest_run (latest run). The description implies a target is needed but the schema makes target optional, causing ambiguity.

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