list_runs

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It reveals that only finished runs are returned and that results are ordered newest first. It does not mention pagination, the default limit, or read-only nature explicitly. Adequate but not comprehensive.

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 a single, efficient sentence that front-loads the core purpose and ordering with no redundancies or extraneous detail. It earns its length.

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 return structure is covered. The description covers the primary use case and filters. Missing guidance on the limit parameter's behavior, pagination, and any prerequisites such as an active session (implied by sibling tools). Reasonably complete for a list operation, but with notable gaps.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It mentions filtering by ticket and outcome, covering ticket_id and outcome, but omits any explanation of the limit parameter. The outcome enum values are in the schema, but ticket_id format is undefined. Incomplete compensation.

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 states a specific verb (list), resource (finished runs), ordering (newest first), and optional filters (ticket or outcome). It clearly distinguishes from siblings like get_run (single run) and delete_run (mutation) by defining a list operation on completed runs.

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 implies usage for enumerating completed runs and mentions optional filters, which suggests when filtering is appropriate. However, it does not explicitly direct the agent to use get_run for single-run lookups or exclude active runs, so the guidance is clear but not fully explicit.

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