Set simulation mode

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond the enum: it does not say what changing the mode affects, whether it must precede meshing, or any persistence/validation behavior, leaving a genuine gap for a mutating setter.

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?

Very short and front-loaded, with the operation stated first. The enum repetition and the log-style rules reference are the only mild noise; overall it is efficient.

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 trivial single-enum setter with full schema coverage and clear annotations, no output schema is needed and the definition is minimally viable. It is nonetheless thin on what the setting influences, which an agent would want when wiring LES/VLES/DNS into a simulation setup.

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 fully enumerated 'mode' field, so the schema does the documentation work. The description only echoes the same enum values and adds no extra meaning such as which mode is appropriate for which scenario, which is the baseline-3 outcome.

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 simulation mode") and enumerates the valid modes, so an agent knows exactly what the tool does. It does not, however, distinguish itself from related siblings like set_turbulence_model or set_numerics, and the enum list merely repeats the schema.

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 statement of when to use this tool versus alternatives, nor any prerequisites (e.g., whether the project must be open or the mesh already built). The bracketed bulc-mcp rules line points at bulc_knowledge_search for rule IDs, which is a cryptic cross-reference rather than actionable usage guidance.

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