blender_msfs_setup_material

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

No annotations are provided, so the description must carry the behavioral burden. It only says 'set up' without disclosing whether the material is created or modified, whether existing properties are overwritten, what 'extensions' are added, or any side effects. This is insufficient for a mutation-oriented tool.

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 wasted words. It is concise and readable, though slightly generic in the verb 'set up.' Still, it earns its place and is appropriately compact for the amount of information it conveys.

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 tool with 9 parameters, an enum, no annotations, and no output schema, the description is too thin. It does not explain whether the material must already exist, whether optional parameters update only the provided values, or what the resulting MSFS extension setup entails. An agent would need to inspect schemas or guess about the tool's behavior.

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 schema already documents all 9 parameters with 100% coverage, so the baseline of 3 applies. The description adds no additional parameter-level meaning, such as relationships between msfs_type and the PBR values, but it does not need to since the schema is complete.

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 clearly identifies the action (set up) and the resource (a material) with a specific domain (flight simulator PBR properties and extensions). It is not a tautology and is distinguishable from generic material tools, though it does not explicitly contrast with specialized siblings like blender_msfs_create_glass_material.

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 phrase 'flight simulator-specific' implies the tool is for configuring MSFS PBR materials, giving some usage context. However, it provides no explicit guidance on when to use this tool versus related material tools, no prerequisites, and no mention of when not to use it.

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