calculate_solar_roi

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

No annotations are provided, so the description carries full burden. It states inputs and outputs, but does not disclose error handling, precision, or side effects. For a calculation tool, this is adequate but not thorough.

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?

The description is concise at three sentences, but the misleading input list harms clarity. Every sentence should add value; the input list is inaccurate.

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 the simple calculation and presence of output schema, the description covers purpose, inputs, and outputs. However, it omits the default value for price_kwh and does not explain how to derive annual_kwh from kW capacity and location production, leaving gaps for an agent.

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 100%, but the description lists 'install cost, kW capacity, location production, kWh price' which does not align with the schema parameters (system_cost, annual_kwh, price_kwh). This mismatch could confuse the agent; the description implies more parameters than exist.

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 clearly states the tool computes solar panel ROI over lifetime, which is specific and distinguishes it from the vast sibling list. It also references list_bundles for related calculators, aiding differentiation.

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 says 'Use for energy audit' and points to list_bundles for related calculators, providing clear context. However, it lacks explicit exclusions or instructions on when not to use this tool.

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