Set all boundaries open

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds the meaningful domain fact that 'faces' are the 6 mesh boundary planes and that omitting the argument defaults to all of them, but says nothing about effect on the FDS input deck or existing boundary/surface assignments.

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 core instruction is front-loaded in a single efficient sentence with no redundancy. The trailing '[bulc-mcp rules] EVAC-002, VENT-002, VENT-004 — bulc_knowledge_search "<id>"' tag is cryptic clutter, but it is compact and plausibly actionable.

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 single-optional-parameter mutation tool with annotations covering safety and a fully documented schema, this is close to sufficient. It still omits the sibling distinction and any statement of downstream effect on the simulation, which are the remaining gaps an agent would face.

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%, including the enum of face tokens and the 'default: all 6' note, so the description merely restates what the schema already provides. Baseline 3 applies when structured data carries the parameter burden.

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 concrete verb and resource ('Set all 6 domain faces to OPEN') plus the selective variant, so the agent knows exactly what the tool mutates. However, it never distinguishes itself from the very similar sibling 'set_open_boundary', so the agent cannot tell which tool to reach for without inspecting both schemas.

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 parenthetical 'or selectively by providing a list of faces' implies when to use the no-arg vs. list-arg form, and the EVAC/VENT rule references hint that compliance context exists. But there is no explicit guidance on when this tool should be preferred over 'set_open_boundary', which covers similar ground.

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