Blender Export

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'Export', implying a write operation, but omits potential side effects like file overwriting, required permissions, long execution time (despite timeout param), or success/failure indicators. The agent gets limited transparency about real-world behavior.

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 12-word sentence efficiently communicates the tool's core purpose. No filler, all information is relevant. Front-loaded with the action and resource. Ideal conciseness.

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?

Despite simple parameters and no output schema, the description omits crucial details: what happens on success (e.g., file created), error conditions, whether the export is blocking, and if the tool returns any feedback. For a tool with 4 parameters and no annotations, more contextual coverage is expected.

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 coverage is 100%, with each parameter described. The description reinforces that 'selectedOnly' controls export of selected vs. whole scene, adding minimal value beyond the schema. Baseline of 3 is appropriate as the description does not significantly enhance parameter understanding.

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 'Export the scene or selected objects to a file format', specifying the verb (export) and resource (scene/selected objects). It distinguishes from sibling tools like blender_create_object or blender_delete_object, all of which involve different actions. No ambiguity.

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 indicates the tool is for export tasks, but provides no guidance on when to use alternatives (e.g., blender_run_python for custom exports) or scenarios where it should not be used. Implied usage is clear, but exclusions or context-aware advice is missing.

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