rhino_import_file

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

The description adds the behavioral context that geometry is added to the current document, which goes slightly beyond the raw verb. However, annotations already convey that this is a mutating (readOnlyHint=false) and non-destructive (destructiveHint=false) operation, so the description does not disclose additional traits like import position, error handling, or performance implications.

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 that conveys the essential action without wasted words. It is appropriately concise for a simple tool.

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 the tool's simplicity (one parameter) and the presence of an output schema, the description is minimally complete. However, it omits potential caveats like whether imports are placed at the world origin or whether existing geometry is affected, and it doesn't mention error conditions. These are minor for a basic import but could confuse an agent expecting more guidance.

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 already fully documents the single parameter (filepath) including supported formats. The description adds no additional meaning about how the parameter should be used, so it meets the baseline but provides no extra value.

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 and resource ('Import geometry from a file') and specifies the target ('into the current document'), making the action unambiguous. However, it does not explicitly contrast with sibling tools like rhino_export or creation commands, though the intent is obvious from the name and context.

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 such as creating geometry manually or using rhino_run_command. The description does not mention scenario-dependent choices or prerequisites (e.g., file existence, format support), leaving the agent to infer usage.

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