science.battery_capacity

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

Annotations already declare readOnly/idempotent/closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: division is not rounded, inputs must be Decimal strings, and the pack-configuration caveat tells the agent what the tool refuses to compute.

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?

Purpose and formulas come first, then mode/validation, then the caveat. Four dense sentences with no filler or repetition.

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?

With an output schema present, return values need no explanation, and the description covers modes, input constraints, and precision behavior. Slightly short of complete because the semantics of value per mode could be stated explicitly.

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 coverage is 0%, so the description carries the full burden and largely meets it: mode names both allowed values plus the default, value is constrained to >= 0, and voltage is defined as a positive Decimal string in volts. Minor gap: the unit of value (Ah vs Wh) is only implied by mode rather than stated.

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?

Names a specific verb+resource ('배터리 용량을 Ah와 Wh 사이에서 변환') and immediately supplies the governing formulas, so the agent can distinguish it from generic conversion siblings like units.energy_convert or engineering.electrical_power.

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 lists the two modes and the default, and adds a clear exclusion: series/parallel pack capacity is not computed, so the whole-pack voltage and capacity must be supplied as a pair. It stops short of naming a sibling alternative, which keeps it from a 5.

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