create_heat_flux_load

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a load is created and gives no information about prerequisites such as an existing model, region, or step, whether an existing load is replaced, required units, or what the response contains. This is a significant gap for a mutating 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 a single clear sentence with no filler or repetition, and the key differentiator ('surface') is included. It is concise, though so terse that it omits behavioral and parameter context that would be valuable for correct invocation.

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 no annotations and low schema coverage, the description is not complete enough for correct invocation. An agent is not told that the named region, model, and step must already exist, what units magnitude expects, or how the tool behaves if a load with the same name already exists. The presence of an output schema reduces the need to document return values, but the missing context is still substantial.

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 should compensate for missing parameter explanations, but it does not mention any parameter. The parameter names such as magnitude, region_name, step_name, and model_name are somewhat self-explanatory, but the description adds no detail about units, allowed values, required relationships, or the meaning of timeout.

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 uses a specific verb ('Create') and a specific resource ('surface heat flux load'), and the word 'surface' differentiates it from the sibling create_body_heat_flux. An agent can tell exactly what this tool does without opening the schema.

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?

No guidance is given about when to prefer this tool over alternatives such as create_body_heat_flux, create_pressure_load, or create_gravity_load. The only implied cue is the word 'surface' in the description, which is not sufficient routing guidance for an agent comparing many load-creation tools.

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