blender_msfs_create_collision_mesh

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, and it only says the tool creates a simplified mesh. It does not reveal whether the source object is preserved or modified, whether a new object is generated, whether the operation is destructive or reversible, or how the collision_type parameter affects the outcome. An agent cannot predict the side effects of invoking it.

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 with no filler, front-loading the verb and resource. It earns its place, though a second sentence clarifying side effects or sibling choice would strengthen the definition without adding bloat.

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?

The tool has no annotations, no output schema, four parameters, and several closely related siblings, yet the description offers only its one-line core function. Missing are the collision workflow context (box vs. convex vs. simplified), the effect on the source object, and any explanation of the enum semantics, leaving an agent under-equipped to invoke it correctly within the larger MSFS export pipeline.

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 baseline is 3: every parameter already has a description, including defaults for simplify and simplify_ratio. The tool description itself adds no meaning beyond the schema, and the collision_type enum values (none/collider/road/water/trigger) remain semantically opaque even though they materially change the result.

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 and resource: 'Create a simplified collision mesh from a source object for physics interactions.' The qualifier 'simplified' plus the word 'mesh' implicitly differentiates it from the sibling tools blender_msfs_create_collision_box and blender_msfs_create_collision_convex, but it never names those alternatives, so the differentiation is implicit rather than explicit.

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 is given on when to use this tool over its direct siblings (collision_box, collision_convex) or the related blender_msfs_tag_collision_type and blender_msfs_decimate_for_lod tools. There are no stated prerequisites, no when-not-to-use conditions, and no indication of where this step fits in the MSFS collision-authoring workflow.

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