Battery Bank Sizing Calculator

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

With no annotations, description carries full burden. It correctly indicates the tool is a calculator returning results, but does not mention if it has side effects, authentication needs, or any assumptions about input ranges. The output format is briefly described but lacks detail on data types or structure.

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?

Three sentences, no wasted words. First sentence states purpose and output, second adds key factors, third lists return items. Front-loaded with main action, every sentence 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?

Given 6 parameters and no output schema, description explains inputs and outputs adequately. It references a dependency on another tool (calculate_power_budget) and covers key assumptions. However, it could be more complete by specifying units for output or constraints on wiring configuration format.

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 100%, so baseline is 3. Description adds context by summarizing how parameters (daysOfAutonomy, depthOfDischargePercent) are used together, but does not add new meaning beyond what schema already provides for each parameter individually.

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?

Description states specific verb 'calculate' with resource 'battery bank size' and mentions inputs and outputs. It clearly distinguishes from sibling tools like calculate_power_budget or calculate_solar_size by focusing on battery bank sizing alone.

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?

Description implies usage after calculate_power_budget by referencing 'daily energy consumption (from calculate_power_budget)', but does not explicitly state when to use this vs other battery-related tools like calculate_battery_config. No exclusion or alternative guidance.

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