io-import

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

No annotations are provided, so the description must disclose side effects. It only says 'import' but does not mention whether it replaces the current scene, adds objects, or any other behavioral implications. This leaves the agent uncertain about the tool's impact.

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?

A single concise sentence that captures the core functionality without redundancy. No filler.

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 straightforward import tool with only two parameters and no output schema, the description is adequate but could benefit from a note on typical behavior (e.g., adding to current scene vs. replacing). It doesn't cause confusion but could be more informative.

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 description adds value by explaining that format is inferred from the extension when AUTO is used, which is not obvious from the schema alone. However, it does not elaborate on the path parameter or the specific format implications beyond the enum list already present.

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?

Clearly states the action (Import) and resource (mesh/scene file), with a specific detail about format inference. This distinguishes it from io-export which is the obvious counterpart.

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?

Does not specify when to use this tool versus alternatives like io-export or asset preparation. It implies import, but offers no guidance on when it is appropriate or what prerequisites exist.

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