Set turbulence model

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety/idempotency profile is covered. The description adds one genuinely useful behavioral fact — that DEARDORFF is the default — but says nothing about whether the change takes effect on the current setup or requires re-running preflight/the simulation.

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 first two sentences are tight and front-loaded with the essential information. The trailing bracketed rule-reference is opaque filler that consumes attention without conveying usable instruction.

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 one-parameter enum setter with annotations and no output schema, the description covers the minimum: what it sets, valid values, and the default. It omits the practical consequence of the change (restart requirement, interaction with set_numerics/mesh settings), which is the main thing an agent would want before invoking it.

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 parameter is a self-describing enum, so the schema does the heavy lifting. The description duplicates the enum list and adds only the 'DEARDORFF (default)' annotation, which is the one value beyond the schema's content.

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?

States a specific verb+resource ('Set the turbulence model') and enumerates the accepted values, so the agent knows exactly what configuration is being changed. It does not, however, distinguish itself from adjacent simulation-configuration siblings such as set_numerics or set_simulation_mode.

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?

There is no guidance on when a given model should be chosen (e.g., which LES model suits which flow regime) or when not to change the default. The cryptic '[bulc-mcp rules] GEN-016, SIM-002 — bulc_knowledge_search "<id>"' line hints at looking up rules but gives no actionable when-to-use condition.

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