physics_setup_heat_boundaries

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

No annotations exist, so the description carries the full burden. It usefully discloses the mapping of boundary categories to physical roles and all default values, but omits mutation semantics: whether existing boundary conditions are overwritten, whether the heat-transfer physics interface must already exist, and whether the operation is reversible.

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?

Front-loaded with the purpose, then a scannable bulleted taxonomy and a per-argument list. The trailing 'Returns: Configuration confirmation' adds little, but overall there is minimal waste.

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 9-parameter mutation tool with no annotations and no output schema, the description covers parameters well but leaves preconditions, overwrite behavior, and failure modes unaddressed. It is adequate but short of complete.

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 0%, yet the description documents all nine parameters, including units and physical interpretation (heat flux = sources, temperature = sinks) and defaults. It stops short of explaining how boundary numbers are obtained, but it compensates well for the empty schema.

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 ('Setup Heat Transfer boundary conditions') and enumerates the three condition families it configures (flux, temperature, convection). It is clearly distinguishable from the acoustic, flow, and PDE boundary siblings, which configure different physics.

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 implies usage by naming the physics interface and boundary categories, but never says when to use this vs. siblings like physics_configure_boundary, physics_setup_pde_boundaries, or physics_boundary_selection, nor any precondition such as needing boundaries from geometry_get_boundaries first.

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