cst_set_adaptive_mesh

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

No annotations are provided, so the description carries the full behavioral burden. It usefully explains that the solver runs multiple passes and refines high-gradient regions until convergence, but it does not state persistence, expected runtime impact, or how it interacts with other mesh settings.

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?

Two sentences, zero waste, and the core action is front-loaded. The second sentence adds useful behavioral context without becoming verbose.

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 simple three-parameter configuration tool with full schema coverage and no output schema, the description provides enough context to call it correctly. The remaining gap is sibling routing against other mesh refinement tools, which is not addressed.

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%, so the schema already documents enabled, threshold, and max_passes with defaults. The description reinforces the convergence behavior but adds no syntax or parameter meaning beyond what the schema provides.

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 gives a specific verb and resource: "Configure adaptive mesh refinement," and explains the underlying behavior. It is clear what the tool does, but it does not explicitly distinguish it from adjacent mesh-related siblings such as cst_add_mesh_refinement or cst_set_mesh_density.

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 says what happens when adaptive meshing is enabled, but gives no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage is only implied by the purpose statement.

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