list-ci-pipelines

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

No annotations are provided. The description does not disclose behavioral traits such as whether the operation is read-only, pagination behavior, rate limits, or side effects. Only a list of example queries is given.

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 concise: one sentence defining the tool plus a list of example use cases. No redundant information, though the use cases could be integrated into a single sentence for tighter structure.

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?

Covers the core purpose and example queries but lacks details on behavior such as pagination (despite pageLimit and pageCursor), sorting, or the difference from similar tools. Missing output schema and annotations leave 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?

Schema coverage is 100% with all six parameters described in the input schema. The description does not add any extra meaning or context beyond what the schema already provides (e.g., filterQuery, filterFrom, filterTo, pageLimit, pageCursor, sort).

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?

Clearly states the verb 'List' and resource 'CI pipeline events' (pipeline runs/executions). Provides specific use cases like 'recent CI builds' and 'failed pipelines', distinguishing it from sibling tools such as 'get-ci-pipeline-events' (likely single event) and 'list_ci_tests'.

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?

Lists example use cases (e.g., 'recent CI builds', 'failed pipelines') indicating when to use. However, it does not provide when-not-to-use guidance or mention alternative tools like 'get-ci-pipeline-events' for single-pipeline queries or 'search_ci_test_events' for test-specific filtering.

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