calculate_pyroprocess_recycling_mass_balance

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

With no annotations provided, the description carries the full behavioral burden. The verb 'Calculates' implies a deterministic, non-mutating operation, and the domain framing (LiCl-KCl electrorefining at A3F) adds useful context. However, it discloses nothing about side effects, assumptions, or limits.

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 zero filler; the domain qualifiers are packaged efficiently. It is terse to the point of omitting useful detail, but every word earns its place.

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. Against that, the tool has two undocumented parameters with defaults and no annotations, and the description gives no hint of how inputs influence the mass balance — leaving gaps for a calculation tool of this specificity.

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%, so both parameters (cadmium_cathode, spent_fuel_batch_kg) are undocumented except for their titles and defaults. The description never mentions either input, so it does not compensate for the coverage gap — e.g. what toggling cadmium_cathode changes or how batch size affects results remains unexplained.

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?

Contains a specific verb and resource: 'Calculates pyroprocessing molten salt (LiCl-KCl) electrorefining mass balance.' The scope is pinned to a concrete domain (EBR-II fuel, Oklo A3F facility), making it unmistakable against siblings like evaluate_coolant_bundle or solve_aurora_system_transient. It stops short of naming or contrasting a sibling, so it falls just below a 5.

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 states what the tool computes but gives no when-to-use guidance, no prerequisites, and no alternatives among the ten sibling tools. Nothing tells the agent under what conditions this calculation is the right call versus, for example, calculate_radioisotope_production_yield.

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