Import CAD model

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

The description adds context that the operation saves the model into the studio, which is a write action consistent with readOnlyHint=false. However, it does not disclose potential behaviors like overwriting existing names, size limits, or validation errors, and annotations already indicate the basic safety profile.

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 sentence that directly states the action, input formats, data source, and destination. It contains no filler or redundant restatements of schema fields, making it efficient and front-loaded.

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?

With 5 parameters, no output schema, and no parameter descriptions, the description is too brief to be complete. It does not explain what happens after saving (e.g., return value, ID), how parameters like color affect the model, or any error scenarios, leaving significant gaps for an agent.

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 only clarifies two parameters: 'format' ('STL or OBJ') and 'encoding' ('text or base64'). It fails to explain the semantics of 'name', 'data', and 'color', which are otherwise left entirely to the schema's bare types and defaults.

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 ('Import'), names the resource ('STL or OBJ model'), and states the destination ('save it in the studio'). This clearly distinguishes it from siblings like load_model (loading existing) and create_model (creating from scratch).

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: when you have STL/OBJ data in text or base64 and want to add it to the studio. However, it does not explicitly state when to use this tool vs alternatives, such as load_model for file-based imports or create_model for model generation.

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