gh_cad_build_pipeline

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the high-level purpose. It does not mention side effects, whether geometry is modified or baked, required CAD state, or what happens to the pipeline after building.

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 with no filler or repetition. It is front-loaded with the verb and resource, though it could have used the brevity to add a bit more operational specificity.

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, four undocumented optional parameters, and no annotations, the description is far from complete. While an output schema exists and may cover return values, an agent still lacks enough information to know what 'operations' should contain, how layers are used, or what the pipeline build entails.

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%, and the description adds no meaning for any of the four parameters: color, operations, source_layer, and target_layer. Parameter names hint at their roles, but the description does not compensate for the complete lack of schema documentation, especially for the vague 'operations' object.

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 states a clear verb ('Build') and a specific resource ('structured Grasshopper computational pipeline'), and indicates the tool bridges AutoCAD geometry and parametric algorithms. It is distinct from the more granular gh_cad siblings, though it does not explicitly name or contrast them.

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?

No guidance is given about when to use this tool versus related gh_cad tools such as gh_cad_set_param_and_solve or gh_cad_tracked_bake. There are no prerequisites, exclusions, or alternative conditions described.

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