blender_import_glb

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return payload (new objects, triangle count, dimensions in metres), but omits whether existing scene content is preserved or replaced, whether the path must exist, and any Blender-session prerequisite.

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?

Two front-loaded sentences with zero filler; the action and its result are both packed in without repetition.

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?

Since no output schema exists, the description's return-value summary is genuinely load-bearing, but for a mutation tool with no annotations and an undocumented parameter it still omits prerequisites and side effects an agent would need before calling it.

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 single path parameter has 0% schema description coverage, and the description adds nothing about it — no format, whether it is absolute/relative, or accepted extensions per-parameter (the format list is global). This leaves the only documented input under-specified.

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?

States a specific verb (Import) and resource (GLB/glTF/FBX) plus the target scope (the open scene), which cleanly separates it from blender_export_glb. It stops short of explicitly naming sibling alternatives, so it is clear but not fully differentiated in-text.

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?

"Into the open scene" implies a prerequisite (a scene must already be open, e.g. via blender_start/blender_open) but never states when to prefer this tool over blender_open or blender_new_scene, and gives no exclusions or failure conditions.

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