Thermal Lumped

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

Reveals the computational model (equations), the radiative HTC check, and the complete return payload. Given readOnlyHint=true, the description adds meaningful context beyond annotations, though it could explicitly note that the tool is non-mutating.

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?

Cleanly structured: formula first, then guidance, then outputs. No filler, but the mathematical notation is dense and could be slightly reorganized for readability.

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?

Without an output schema, the return values are fully spelled out. The model and key usage caveats are covered. Minor gaps: no explicit units for inputs (e.g., mass_g, area_mm2 are implied by names but not stated) and no note on typical value ranges.

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?

With 0% schema description coverage, the description compensates for c_p (explicit vs material), h_conv source, duration_s behavior. It doesn't explain emissivity, t_ambient_c, mass_g, power_w, area_mm2 beyond their names, leaving some ambiguity for an agent.

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, and scope: 'Lumped first-order transient warm-up (no mesh)'. The physics and outputs are enumerated. It is clearly distinguishable from mesh-based thermal tools like thermal_transient_submit.

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?

Explicitly tells the agent to obtain h_conv from the h_estimate correlation screen rather than guessing, and describes when duration_s is relevant. This routes the agent to the correct companion tool and clarifies input strategy.

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