set_pipe_parameters

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

Annotations are absent, so the description carries the full burden. It discloses units for several parameters, which is useful, but it does not explain whether the tool overwrites all parameters, how null defaults are interpreted, or whether the case must already exist. This is a significant gap for a mutation-like 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 two sentences with no filler. The main purpose is stated first, and the units sentence provides essential context without redundancy.

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?

Given 8 parameters, no schema descriptions, no annotations, and the complexity of a simulation workflow, the description is too sparse. It omits crucial context such as the requirement for an existing case, the meaning of mesh-resolution parameters, and the behavior when optional parameters are left as null. The presence of an output schema does not mitigate these gaps.

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 description groups parameters into categories (geometry, fluid properties, mesh resolution) and specifies units for length, viscosity, density, and velocity. However, it does not explain n_axial and n_radial beyond 'mesh resolution' and does not clarify the null-default semantics. With 0% schema coverage, the description only partially compensates.

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 states the tool's action ('Set') and resource ('Hagen–Poiseuille pipe geometry, fluid properties, and mesh resolution'). It distinguishes the tool from siblings like generate_mesh and start_solver, though it does not explicitly mention that parameters are set on an existing case.

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 provides no guidance on when to use the tool relative to its siblings, e.g., after creating a case and before generating a mesh. It also does not mention any prerequisites or alternatives.

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