search-ci-pipelines

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

No annotations are present, so the description carries full burden. It mentions 'query filtering' but fails to disclose key behavioral traits such as return format, pagination, rate limits, or that it retrieves events. The schema covers the 'limit' parameter, but the description adds no behavioral context beyond the schema itself.

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 sentence that is concise and to the point. However, it could be structured to front-load the most critical action (searching) and the specific resource (CI/CD pipeline events). No wasted words, but lacks detail.

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 5 parameters (2 required) and no output schema, the description is insufficient. It does not explain what type of events are returned, how to interpret results, or typical use cases. An agent would struggle to understand the tool's full capabilities from this description alone.

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 100%, so each parameter has a description in the schema. The tool description adds no additional meaning beyond stating 'with query filtering,' which is already implied by the 'query' parameter. Baseline score of 3 is appropriate.

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 states the verb 'Search' and the resource 'CI/CD pipeline events (builds, deploys)' with query filtering. It effectively communicates the tool's core function but does not explicitly distinguish it from sibling tools like 'search-ci-tests' or 'aggregate-ci-pipelines'.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Without context on when to choose it over similar tools, agents may misuse it.

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