Review Pipeline

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

The description adds valuable behavioral context beyond the annotations: it explains the tool walks the node DAG, inspects transforms, join conditions, etc., and returns findings sorted by severity. Since annotations already declare readOnlyHint and idempotentHint, the description enriches with operational details without contradicting annotations.

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 well-structured with a concise opening sentence followed by bullet points listing specific checks. Every sentence adds value; no fluff. It is appropriately sized for the complexity of the tool.

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's complexity, the description fully covers what it does, the checks performed, and parameter usage. The presence of an output schema means return values need not be detailed. The description is complete for an agent to understand when and how to invoke the tool.

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?

Input schema covers both parameters with descriptive descriptions (100% coverage). The description's additional note about using nodeIDs to scope the review largely repeats schema info, adding minimal new meaning. Baseline 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 tool's purpose: 'Analyze an existing pipeline in a Coalesce workspace and suggest improvements.' It specifies the verb 'analyze' and the resource 'pipeline', and enumerates specific checks (e.g., redundant passthrough nodes, missing join conditions, layer violations), making it highly distinct from siblings like analyze_impact or analyze_workspace_patterns.

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 the tool (when reviewing an existing pipeline) and mentions scoping via nodeIDs, but it does not explicitly state when not to use it or suggest alternative tools for different scenarios. Provides basic usage context but no comparative guidance.

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