solve_aurora_system_transient

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

With no annotations, the description carries the full disclosure burden. It does reveal genuine behavioral semantics beyond the schema: the tool is an orchestration of eight solvers executed in sequence, which implies compounding runtime and coupled dependencies. However, it says nothing about cost, execution time, permissions, or whether any state is mutated or persisted, so the safety/effort profile remains opaque.

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, front-loaded sentence with no filler or repetition. It is efficient, though arguably undersized for a composite 8-solver tool whose inputs are entirely undocumented, so the terseness shades slightly into under-specification.

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?

An output schema exists, so return values need not be explained. But given no annotations, four undocumented parameters, and a tool whose behavior is a chain of eight solvers, the description leaves too much unstated: it never says when to prefer this over the individual sibling solvers or what the scenario actually produces. Adequate as a one-line identity, insufficient as a complete definition.

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?

All four parameters have 0% schema description coverage and the description mentions none of them. The names are partially self-documenting through embedded units (power_mwth, coolant_flow_kg_s, coolant_inlet_temp_c), but for a 4-parameter multi-physics driver the description should clarify what the inputs drive and how the defaults (4 MWth, 12.5 kg/s, 100 kg, 360 C) shape the scenario. It does not compensate for the coverage gap.

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 names a concrete action ('chains ... solvers sequentially') and its scope ('all 8 fast-reactor & ecosystem solvers', 'unified multi-physics evaluation scenario'). This implicitly distinguishes it from the sibling tools, which each evaluate a single domain (core conduction, coolant bundle, RVACS, etc.). It stops short of explicitly saying it is the composite counterpart of those siblings, but the resource and scope are clear.

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?

Usage is implied rather than stated: an agent can infer this is the tool for a whole-system multi-physics run as opposed to the single-domain siblings. There is no explicit when-to-use/when-not-to-use, no guidance on preferring the individual solvers for targeted questions, and no cost or runtime caveat for invoking the full chain.

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