blender_export_glb

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the key scoping default (whole scene when objects is omitted), which is real behavioral context, but it omits file overwrite behavior, path resolution rules, and any Blender server/connection requirements for a write-to-disk operation.

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 short sentences, zero filler, and the scoping rule is front-loaded right after the core action. Every clause earns its place.

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 simple 2-parameter export with no output schema, the description resolves the main ambiguity (object filtering) but leaves the required `path` parameter and connection/prerequisite context unexplained. Adequate but with clear gaps.

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 the description must compensate. It explains the `objects` parameter's effect (export only the named objects vs the whole scene) but says nothing about `path` (format, relative vs absolute, overwrite semantics), leaving half the parameters undocumented.

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 and target format ('Export to a .glb'), which is clear and actionable. It does not explicitly contrast with the sibling blender_import_glb, but the export direction is unambiguous from the name and description.

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 conditional 'With `objects`, only those; otherwise the whole scene' tells the agent how the scope parameter changes behavior, which is useful. However, it gives no guidance on when to choose this over alternatives or any prerequisites (e.g., Blender must be running, scene must be loaded).

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