blender_msfs_get_material_presets

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

No annotations are provided, so the description alone must convey behavioral traits. The verb 'Get list' strongly implies a read-only, non-mutating operation, but the description does not explicitly state that it has no side effects or that it requires no setup. It also does not disclose whether the list comes from local data or an MSFS installation.

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 delivers the core function plus illustrative examples. There is no wasted wording, and the key action is front-loaded.

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 zero-parameter retrieval tool, the description is nearly complete: it states what is returned (a list of presets) and gives examples. Since no output schema exists, a bit more detail about the exact return format or how the presets relate to sibling setup tools would improve completeness, but the current description is sufficient for basic invocation.

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?

The tool has zero parameters and the schema coverage is 100%, so the description has no parameter burden to carry. The examples (vehicle_paint, chrome, glass) add useful semantic context about the values returned, which is a small bonus beyond the empty schema.

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 ('Get list') and resource ('available flight simulator material presets') with concrete examples (vehicle_paint, chrome, glass), making the tool's function clear. It is implicitly distinguished from sibling material tools like blender_msfs_setup_material, but it does not explicitly name any alternative or contrast behavior.

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 description implies this tool is for retrieving preset options, likely before configuring materials, but it gives no explicit when-to-use guidance or exclusion criteria. It does not mention alternatives or conditions under which a different material-related tool should be selected.

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