blender_export

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

No annotations provided, so description must disclose behavioral traits. It doesn't mention side effects (e.g., file overwriting, scene modification), error handling, or export limits. Only lists operations without behavioral details.

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?

Short and front-loaded, but the bullet list for operations is minimal. Could be more structured (e.g., grouping parameters by operation). Adequate but not highly efficient for an agent.

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?

With 9 parameters, 0% schema coverage, and no annotations, the description is far from complete. It doesn't explain output format, error scenarios, or how operations interact with parameters. Even with an output schema, major gaps remain.

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 0%, so description must compensate. It explains operation and hints at file_format via bullet points, but 7 of 9 parameters (e.g., global_scale, apply_transforms) are undefined. No parameter-level descriptions.

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 tool exports Blender scenes/objects to interchange and game-engine formats. Lists specific operations (glTF, FBX, etc.) and platform presets, distinguishing it from sibling tools like blender_import or blender_render.

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 on when to use each operation, how presets differ from manual format selection, or prerequisites. The sibling blender_export_presets exists but isn't referenced, and the description doesn't help an agent choose between options.

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