List pipelines

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

No annotations exist, so the description must disclose behavior on its own. It adds 'newest first' ordering and the set of filter dimensions. But it omits pagination behavior (though schema covers page/per_page), what 'recent' means, and doesn't explicitly state read-only/non-mutating nature.

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?

Two sentences with no filler. First states purpose, second adds filter guidance and a concrete example. Ideal size.

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?

For a list tool with 7 params but no output schema or annotations, the description covers the core operation, ordering, and filters. It falls slightly short of fully complete because 'recent' is vague and there's no mention of return format, but the schema and sibling names cover much of the gap.

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 coverage is 100% – every parameter has a description. The description only mentions branch/event/status filters, which are already documented in schema, without adding new semantic detail. Baseline 3.

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 opens with 'Lists recent pipelines for a repository, newest first' – a specific verb, resource, and ordering. The filter guidance and example clarify it targets the list-level operation, distinguishing it from get_pipeline (single pipeline) and list_repos (repos).

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?

Gives context for when to use: filtering by branch/event/status to find 'CI runs for a pull request branch.' However, it doesn't explicitly compare to sibling tools like get_pipeline for single-pipeline lookups, so no exclusions or alternatives are named.

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