Export CAD model

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

Annotations already cover read-only and non-destructive behavior. The description adds that the model must be 'saved' and that output is 'ASCII STL or OBJ data,' but does not clarify how the data is returned (e.g., direct binary, base64, file URL) or any error behaviors, leaving some ambiguity.

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, front-loaded sentence of nine words. Every word contributes meaning, with no unnecessary detail or repetition.

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?

The tool has only two required parameters and no output schema. The description gives the essential operation and formats, but it fails to specify the exact return structure (e.g., plain text, binary, base64-encoded) which is important in the absence of an output schema. It is adequate for a simple export but 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?

With schema description coverage at 0%, the description partially compensates by explaining that 'stl' means ASCII STL and that format choices are STL or OBJ. However, it does not explicitly describe the modelId parameter, leaving it to be inferred from 'saved CAD model' and the schema's UUID format.

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 function: 'Export a saved CAD model as ASCII STL or OBJ data.' It uses a specific verb ('Export') and resource ('saved CAD model') and differentiates from siblings like import_model and load_model by focusing on file data extraction.

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 provided on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites beyond 'saved', or distinctions from load_model or import_model. The context is only implied, not explicit.

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