Validate project pipeline

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

Annotations already declare readOnlyHint=true. The description adds specificity by noting the pipeline must be 'already saved' and that validation does not involve execution. This goes beyond the generic read-only flag and provides meaningful context about prerequisites and non-mutation.

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, concise sentence that front-loads the verb and object. It contains no filler and every word contributes to understanding the tool's purpose.

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?

The tool has 6 parameters and no output schema, yet the description does not explain what validation returns, the role of optional parameters, or any validation behavior beyond 'without executing.' Given the complexity and lack of schema descriptions, this is incomplete.

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?

The schema has 6 parameters with 0% description coverage. The description does not mention any parameter, required or optional. With low schema coverage, the description must compensate, but it fails to explain what parameters like pipeline_id, env_name, variables, or service_names mean. This is a significant gap.

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 action ('Validate') and the resource ('an already saved project-level pipeline'), and distinguishes it from execution by adding 'without executing it.' This differentiates it from sibling tools like deploy_project_pipeline and preview_pipeline_template.

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 implies when to use: to validate a saved pipeline without execution. It explicitly excludes execution, but does not name alternative tools for when execution is needed. This provides clear context without explicit alternatives.

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