geometry_import

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

No annotations exist, so the description carries full burden. It mentions 'Import geometry' and 'Returns: Import operation info' but does not disclose whether the tool modifies existing geometry, overwrites, or requires an active model. Side effects and permissions are absent.

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 relatively short and uses a structured 'Args' and 'Returns' format. However, the docstring-style repetition of parameter names could be condensed, and the 'Returns' part adds little beyond the obvious.

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?

For a CAD import tool with multiple parameters and supported formats, the description lacks critical context: whether a model must be open, how the import interacts with existing geometry, and what 'Import operation info' actually contains. No output schema exacerbates the gap.

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 coverage is 0%, so the description must add meaning. The 'Args' section provides brief descriptions for each parameter (e.g., 'Path to the CAD file', 'Geometry sequence name'), which is helpful but lacks details like allowed values for import_type or format-specific constraints.

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 verb 'Import' and resource 'geometry from a CAD file', with a list of supported formats (STEP, IGES, STL, NASTRAN). This distinguishes it from sibling tools like geometry_add_* that create primitive shapes rather than import files.

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 lists supported formats, implying the tool is for importing external CAD files, but does not explicitly state when to use it versus alternatives like geometry_create or geometry_add_feature. No when-not-to-use guidance or prerequisites (e.g., existing model) are provided.

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