import_cad_file

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

No annotations are provided, so the description bears full responsibility. It describes the pipeline (detect, convert, import) and mentions conversion tool selection, but fails to disclose important behaviors such as whether it modifies the current scene, creates new objects, handles errors, requires internet for some conversion tools, or has side effects like overwriting existing data.

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 moderately sized (5 lines) with a clear front-loaded purpose and a structured list of pipeline steps. It is efficient but could be slightly more concise by removing redundancy (e.g., the pipeline list largely restates the opening sentence).

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?

Despite having an output schema (not shown in description), the description does not mention return values, success/failure indicators, or error handling. Given 8 parameters and no annotations, the description leaves significant gaps, such as what happens after import and how to interpret results.

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?

The input schema has 100% description coverage, so the baseline is 3. The description does not add additional meaning beyond the schema; for example, 'filepath' is simply 'Path to CAD file' in both. No extra semantic context is provided.

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 explicitly states 'Import CAD files (STEP, IGES) into Blender with automatic conversion', specifying the verb (import), resource (CAD files), and target (Blender). It also outlines a clear three-step pipeline, distinguishing it from generic import tools like 'blender_import' by focusing on CAD-specific conversion.

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or compare with other import tools or sibling tools. While the purpose implies usage for CAD files, there is no direct advice for agent decision-making.

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