review_cicd_pipeline

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

With no annotations, the description carries the full burden. It usefully discloses the output shape ('severity-tagged findings and recommended fixes'), which matters because there is no output schema. But it says nothing about whether the tool only reads (no mutation of the pipeline), size limits on config input, or how findings are scoped, leaving the safety profile unstated.

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, zero filler; the purpose and validation dimensions are front-loaded, with the return behavior second. Nothing is restated from the title or schema.

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 three-parameter analysis tool with no output schema, the description covers what it does and what it returns, which is the key missing structured information. It stops short of stating input constraints (e.g., supported config formats, size limits) or how it relates to the other review_* tools.

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 pipelineType, pipelineConfig, and context are already documented, including the platform enum. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (validate) and resource (CI/CD pipeline configuration) and enumerates the review dimensions (correctness, security, efficiency, best practices). The resource is narrow enough to be told apart from review_code, review_architecture, and review_infra_config, though no sibling is named explicitly.

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?

Usage is implied by the narrow resource — an agent can infer this applies to pipeline configs rather than general code or infra. However, there is no explicit when-to-use guidance, no exclusions, and no routing advice against the neighboring review_* and review_infra_config tools.

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