blender_msfs_batch_export_lods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the single-file versus separate-files behavior, but leaves 'proper structure' vague and does not disclose whether files are overwritten, whether existing LOD hierarchies are required, or how the export affects the Blender scene.

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 a single efficient sentence that front-loads the primary action and key output modes. The phrase 'proper structure' is somewhat vague, but overall the description is appropriately concise.

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?

This is a file-export tool with no annotations and no output schema, and the description is too minimal for the complexity of MSFS LOD workflows. It does not mention prerequisites, file formats, relationship to the LOD setup pipeline, error conditions, or how the result will be named or organized beyond the separate-files toggle.

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 100%, so the schema already documents all three parameters. The description only loosely restates the separate_files behavior ('single file or separate files per LOD') and adds no extra meaning about base_name or output_dir, so the baseline score of 3 is appropriate.

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 states a specific verb ('Export') and resource ('LOD hierarchy'), and adds a meaningful distinction with 'single file or separate files per LOD.' It is clear on what the tool does, though it does not explicitly differentiate from the sibling blender_msfs_export_model, so a top score is not warranted.

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 on when to use this tool versus related tools like blender_msfs_create_lod_hierarchy, blender_msfs_setup_lod_distances, or blender_msfs_export_model. The description implies the purpose but provides no context, prerequisites, or exclusions.

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