validate_pipeline

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

With no annotations provided, the description must disclose behavioral traits itself. It only states that it validates, but does not explain side effects (e.g., whether it reads or writes, returns errors on failure, or is safe/destructive). The lack of any behavioral detail beyond the validation action is a significant gap for a tool with no annotation coverage.

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 with no filler words. It front-loads the key action and resource, making it efficient. However, it may be too terse for the tool's complexity, but conciseness itself is well-handled.

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 three parameters with nested objects, no annotations, and no schema descriptions, the description is woefully incomplete. It provides no context on return values, validation failure behavior, prerequisites, or how it fits into the broader export workflow. Although an output schema exists, the absence of parameter explanations and behavioral guidance leaves the agent unable to invoke this tool correctly.

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 0%, so the description must compensate by explaining the parameters. It mentions 'pipeline spec' and 'optional CPU Tensor boundary' but doesn't explicitly map these to the three schema properties (pipeline, target, input_contract). The parameter meanings remain ambiguous (e.g., which parameter is the 'CPU Tensor boundary'?), adding minimal value beyond the schema field names.

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 tool's function: 'Validate a pipeline spec and optional CPU Tensor boundary before export.' It uses a specific verb ('validate'), specifies the resource ('pipeline spec'), and provides temporal context ('before export') that distinguishes it from related tools like export_pipeline.

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 phrase 'before export' implies when to use this tool (as a pre-export step), but it provides no explicit guidance on when not to use it or how it compares to alternatives such as adjust_pipeline or explain_pipeline. There are no exclusions or alternative tool references, so the usage context is only implied.

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