blender_msfs_validate_for_export

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, but it only says 'validate... and report issues.' It does not state whether the operation is read-only or mutates the model, which specific compatibility checks are performed, or how issues are returned. The term 'report issues' hints at output but leaves the agent guessing about side effects and result format.

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 nine-word sentence with no filler; the action verb is front-loaded and every word carries meaning. 'Validate' states the action, 'for flight simulator compatibility' gives the domain, and 'report issues' discloses the output. This is appropriately sized for a tool with one optional parameter.

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 the tool's surface simplicity, MSFS validation is domain-specific and the description does not say what compatibility criteria are checked, what issue types are reported, or whether the call is safe/non-destructive. There is no output schema or annotation to fill these gaps, and no relationship to the export workflow is stated. An agent cannot reliably predict what happens when it invokes this tool or how to act on the result.

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 the single optional parameter object_name is already well documented ('Specific object to validate (omit for all selected/all)'), so the baseline is 3. The description's plural 'model(s)' loosely aligns with the parameter's scene-level default but adds no format, naming, or usage detail beyond the schema. Nothing in the description compensates for or contradicts the schema, so a baseline score 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 ('Validate'), a resource ('model(s)'), and a distinguishing domain ('flight simulator compatibility'), and states the output behavior ('report issues'). This separates it from generic validation siblings like blender_validate_dimensions and blender_validate_mesh_quality. It loses a point because 'model(s)' is slightly ambiguous and it doesn't explicitly name what it is not.

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 versus alternatives such as blender_validate_mesh_quality, blender_validate_dimensions, or blender_msfs_livery_validate_package. There is no mention of prerequisites (e.g., run before export, select objects first) or exclusions. Usage context is only weakly implied by the MSFS prefix in the tool name.

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