Solar Panel Sizing Calculator

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

With no annotations, the description alone must disclose behavior. It states the tool accounts for losses and returns wattage and configurations, implying a read-only calculation. However, it does not explicitly state that no data is modified, nor does it discuss authentication or side effects. Reasonable for a calculator but could be more explicit.

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 extremely concise with two sentences, no filler. First sentence presents the core purpose, second adds key details. 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?

The tool has no output schema, so the description must convey return format. It only says 'returns required wattage and common panel configurations' without details on structure. Given 3 parameters and no annotations, the description is adequate but incomplete regarding output.

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%, and parameter descriptions are detailed (e.g., examples for peakSunHours). The description adds context about what the tool accounts for (peak sun hours, efficiency) but does not add significant meaning beyond schema. Baseline 3 is appropriate.

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's purpose: to calculate required solar panel wattage based on daily consumption, peak sun hours, and system efficiency. This is a specific verb+resource pair that distinguishes it from sibling tools like calculate_power_budget or calculate_battery_bank.

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 implies usage for sizing solar panels after obtaining daily consumption, but it does not explicitly state when to use versus alternatives, nor does it mention prerequisites or when not to use. Two sentences provide context but lack explicit guidance.

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