Inverter Sizing Calculator

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

Without annotations, the description carries the full burden. It discloses that the tool accounts for continuous power, startup surge power (with typical multiplier), and a 25% headroom. It also states the return values (recommended wattage and DC current). This is good transparency for a calculator tool, though it could mention if any default assumptions are made about inverter efficiency.

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: two sentences, no wasted words. It front-loads the purpose and immediately follows with behavioral details. 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?

With 100% schema coverage and no output schema, the description adequately covers inputs and outputs. It explains the main calculation factors (surge, headroom) and what is returned (wattage, current). However, it does not mention edge cases or failure modes (e.g., invalid voltage), which would push it to 5.

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% (baseline 3). The description adds significant value beyond the schema by explaining how parameters are used: 'Accounts for continuous power, startup surge power... includes a 25% headroom'. This gives the AI agent meaningful context about the calculation logic.

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 verb 'Calculate' and the resource 'inverter size', and specifies the context: 'running AC loads from a DC battery system'. This distinguishes it from sibling tools like calculate_battery_bank or calculate_solar_size, which have different purposes.

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 does not provide explicit guidance on when to use this tool versus its siblings. For example, it doesn't state that this should be used after determining battery capacity or solar size. The tool's purpose is understandable from context, but the lack of explicit usage hints limits its helpfulness for an AI agent.

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