blender_msfs_export_model

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose output format (MSFS-compatible glTF) and included categories (LODs, collision, animations), which is meaningful. However, it does not mention overwrite behavior, prerequisites, validation needs, or what happens when objects are omitted, leaving several behavioral aspects undisclosed.

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 front-loaded sentence with no filler. Every phrase contributes meaning: the verb, the MSFS target, the glTF format, and the specific included data types. It is as concise as possible while still distinguishing the tool from generic exporters.

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 6-parameter MSFS pipeline tool with no annotations and no output schema, the description is adequate but thin. It does not mention preparation steps such as creating LOD hierarchies, collision meshes, or validating the scene before export, nor does it explain the relationship to sibling tools like blender_msfs_validate_for_export, so an agent may miss important workflow context.

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%, and all parameters already have clear descriptions with defaults and enums. The description's mention of LODs, collision, and animations loosely mirrors three boolean parameters but adds no parameter-level detail beyond the schema, so the baseline 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 uses a specific verb ('Export') with a clear resource ('model(s)') and a distinctive target format ('flight simulator-compatible glTF'), and it names the included contents (LODs, collision, animations). This clearly differentiates it from generic export siblings like blender_export_gltf or blender_export_obj.

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 MSFS qualifier and inclusion list imply this is the MSFS-specific export path among many generic export tools, but there is no explicit when-to-use/when-not-to-use statement. It does not point to alternatives such as blender_export_gltf or preparation tools like blender_msfs_validate_for_export, so an agent must infer context from the name and sibling set.

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