Combine CAD models

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

Annotations already declare readOnlyHint=false and destructiveHint=false, indicating a non-destructive write operation. The description adds the operation types but does not disclose additional behavioral traits such as whether the original models are unchanged, if the result is saved automatically, or any permission requirements. Minimal added value beyond 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 a single, direct sentence that conveys the core functionality without verbose or redundant phrasing. It earns high marks for efficiency and front-loading the key action.

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?

This tool has no output schema, so the description should describe what the operation returns or whether the new model is persisted. It also lacks explanations for all parameters, particularly 'name' and 'color', and does not mention the relationship to sibling tools or any side effects. Given the moderate complexity and missing schema descriptions, the description is not fully complete.

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. It clarifies that modelIds must include two or more saved models and lists the three operation values, but it does not explain the 'name' or 'color' parameters. The 'name' likely refers to the resulting model's name and 'color' its appearance, but this is left to inference, which is insufficient for a fully self-contained tool.

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 a specific verb 'Create' and resource 'new model', and clearly specifies the boolean operations (union, difference, intersection) on two or more saved models. This differentiates it from siblings like create_model (which likely starts from scratch) and transform_model (which modifies a single 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 implies usage for combining existing models via boolean operations, but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. There is no mention of alternative tools like transform_model for single-model edits, so guidance is limited.

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