blender_import_model

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

Annotations already indicate this is not read-only and is not idempotent, and the description adds that importing creates objects and returns their names. However, it does not disclose whether objects are appended to the current scene, placed in a specific collection, or how failures such as missing files are handled.

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 two short sentences with no filler. It front-loads the core purpose, lists formats compactly, and ends with the return behavior, making every word useful.

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?

The description covers the essential import behavior and return value, which is enough for basic use. However, it omits the semantics of the 'collection' parameter, placement behavior in the scene, and guidance on using importer-specific properties, leaving meaningful gaps for an agent without an output schema.

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 50%, and the description helps clarify the 'path' parameter by listing accepted formats. The schema itself covers 'properties' and 'response_format', but the 'collection' parameter remains unexplained in both the schema and description, so the description only partially compensates for the coverage gap.

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 uses a specific verb and resource: 'Import a 3D model from disk', lists supported file formats, and states that the tool returns the names of created objects. It is clear and distinguishable from related tools like blender_export_model, though it does not explicitly name sibling alternatives to differentiate itself.

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?

There is no guidance about when to use this tool versus alternatives such as blender_open_blend, especially since .blend files are included in the supported formats. The usage context is only implied by the tool name and description, not explicitly stated.

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