rhino_cmd_import

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions importing geometry into the current document, which implies mutation of the active document, but does not explain side effects, failure modes, supported file formats, or how the returned 'Dict with command result' reflects success or errors. The vague return statement adds little transparency.

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 reasonably compact and front-loaded with the core purpose. However, the Args/Returns formatting includes a `controller` parameter that does not appear in the schema, and the return description is vague enough to be of limited use. It is not excessively verbose, but not every sentence adds clear value.

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 mutation-oriented tool with no annotations and minimal schema coverage, the description is incomplete. It lacks supported file formats, behavior when importing into a non-empty document, error handling, and any distinction from similar import tools. An agent would need more context to invoke it correctly and interpret the result reliably.

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 schema covers 0% of parameter semantics, so the description must compensate. It does explain `file_path` as an 'Absolute path to the file to import', which is helpful. However, it also lists `controller: RhinoController instance` as an argument even though the input schema only defines `file_path`, creating potential confusion about required parameters.

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 action ('Import geometry from an external file') and the destination ('into the current document'). This is a specific verb+resource statement that distinguishes the basic import behavior from creation or document-level operations, though it does not explicitly differentiate from the sibling `rhino_import` tool.

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 gives no guidance on when to use this tool instead of alternatives such as `rhino_import`, `rhino_open_file`, or `rhino_open`. There are no exclusions, prerequisites, or context about file formats or document state, leaving the agent without enough information to choose between similar import-related tools.

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