list_ci_pipelines

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'optional filtering' but doesn't describe key behaviors like pagination (implied by the cursor parameter but not explained), rate limits, authentication requirements, or what the output looks like (especially given no output schema). For a list operation with 6 parameters, this leaves significant gaps in understanding how the tool behaves.

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 ('List CI pipelines from Datadog CI Visibility') and adds a useful qualifier ('with optional filtering'). There is no wasted language, and it's appropriately sized for a list operation with filtering capabilities.

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 complexity (6 parameters, no annotations, no output schema), the description is insufficiently complete. It doesn't explain the output format (e.g., what data is returned, structure), pagination behavior (cursor usage), or error handling. For a tool that likely returns structured data from a CI system, more context is needed to help the agent use it effectively.

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%, meaning all parameters are well-documented in the schema itself. The description adds minimal value beyond the schema by mentioning 'optional filtering,' but it doesn't provide additional context like typical use cases for filters or interactions between parameters. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't significantly enhance parameter understanding.

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 ('List') and resource ('CI pipelines from Datadog CI Visibility'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_pipeline_fingerprints' or 'list_metrics', which could also relate to pipelines or CI data. The optional filtering mention is helpful but doesn't provide sibling differentiation.

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 like 'get_pipeline_fingerprints' or other sibling tools. While it mentions optional filtering, it doesn't specify scenarios where this tool is preferred over others, nor does it mention any prerequisites or exclusions. The agent receives no contextual usage instructions.

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