Create CAD model

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

Annotations provide only that the tool is not read-only and not destructive. The description adds that it creates a model from a parametric shape tree and enumerates supported operations, giving the agent insight into input capabilities. However, it does not disclose side effects like name conflicts, return values, or permissions, which would be valuable.

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, focused sentence that front-loads the primary action and then lists supported capabilities. Every word adds value, and it is easy to scan.

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 highly complex nested shape schema and lack of output schema, the description gives a helpful summary but omits important operational details such as naming constraints, return value, or error conditions. It tells the agent what the tool can do, but not enough about the results or side effects for a fully informed invocation.

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?

With 0% schema description coverage, the description's mention of 'primitives, extrusions, transforms, mesh input, and boolean operations' adds high-level meaning to the complex 'shape' parameter. However, it does not explain the 'name' or 'color' parameters, though their schema definitions are self-explanatory. The description partially compensates for the missing schema descriptions.

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 uses the specific verb 'Create' with resource 'CAD model' and clearly states the input is a 'declarative parametric shape tree'. It lists supported features (primitives, extrusions, transforms, mesh input, boolean operations), which distinguishes it from sibling tools like list_models, update_model, or delete_model.

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 does not mention when to use this tool versus alternatives. While 'Create' implies using it to make a new model, it does not differentiate from generate_model or import_model, nor does it state any exclusions or prerequisites. Usage is only implied by the name and title.

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