import_geometry

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

With no annotations, the description is the only source of behavior. 'Import a geometry' implies adding geometry, but it does not say whether it overwrites existing geometry, whether it requires an active model, or what error behavior occurs for unsupported formats. Important side effects and requirements are undisclosed.

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 sentence is short and front-loaded, with no filler words, so it is concise. However, its brevity sacrifices the substance needed to structure parameter and usage details.

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 that import_geometry is a non-trivial operation with three undocumented parameters, no annotations, and an unseen output schema, the single-sentence description omits critical context about supported file types, required model state, and side effects. An agent cannot reliably invoke it without additional information.

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 loosely hints at the file format. It does not explain the purpose of 'geom_tag' (likely an identifier but ambiguous), what values 'type' accepts, or what 'filename' refers to relative to the server. This is insufficient for correct parameter construction.

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 states a clear verb ('Import'), object ('a geometry'), and source ('from a CAD/file format'). This differentiates it from sibling primitives like add_sphere and add_block, but 'CAD/file format' is left unspecified, and the exact outcome (e.g., new geometry tag vs replacing a model) is unclear.

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 given for when to use import_geometry over sibling tools such as add_sphere or generate_model_java, nor any mention of prerequisites like having a model loaded or a valid file path. The description is purely functional, leaving selection to inference.

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