simulate_passive_rvacs_cooling

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 describes the physics being modeled but doesn't state whether the simulation is deterministic, what units the output uses, time-step behavior, or any limits. With no annotations and no output-schema explanation in the description, this is a significant gap.

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?

A single, dense sentence that front-loads the core simulation purpose. It's efficient and not padded, though the acronym expansion adds length without operational guidance.

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 simulation tool with no annotations, 3 undocumented parameters, and an output schema, the description omits parameter meaning, output interpretation, and usage context. It's too sparse for correct invocation despite the explicit scenario.

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% and there are 3 parameters with no descriptions. The description doesn't mention power_mwth, duration_hours, or initial_sodium_temp_c at all, so an agent gets no semantic help beyond parameter names and defaults.

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 states a specific simulation verb and resource (1D passive RVACS natural air circulation decay heat removal), and includes the triggering scenario (LOFF reactor trip). This distinguishes it from siblings like solve_aurora_system_transient or evaluate_coolant_bundle. However, it doesn't explicitly name which sibling to use instead in adjacent cases.

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?

It implies usage through the LOFF reactor trip scenario, giving a clear context for when this simulation applies. But it offers no exclusions, no alternatives, and no guidance on when to pick a different sibling (e.g., solve_aurora_system_transient).

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