calculator

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

With no annotations provided, the description carries the full burden. It discloses the formula, the factors involved, and the output format (kg, bags, pallets). It does not explicitly state that this is a read-only calculation, but the nature of the tool makes that implicit; the formula transparency adds value beyond a simple 'calculate'.

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?

Two sentences with dense, relevant information. The purpose is front-loaded, and the formula and output units are included without extraneous wording. 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?

For a calculation tool, the description covers the purpose, the formula, and the output units. The schema covers all parameter details, so no additional parameter documentation is needed. The tool is fully specified for an agent to invoke it correctly.

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?

Although the schema already describes each parameter (100% coverage), the description enriches them by mapping them to the formula: boiler_kw, insulation, desired_temp, and heating_months feed into the factors. This clarifies their role in the calculation beyond the schema's simple labels.

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 a specific action ('Calculate heating fuel needs') and the resource ('boiler specs'). It also names the output units (kg, bags, pallets), making the tool's purpose unambiguous and distinct from its unrelated siblings.

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 when to use the tool: when heating fuel needs must be calculated from boiler specifications. It does not explicitly state exclusions or alternative tools, but given the sibling set is unrelated to this calculation, the clear context is sufficient for an agent to decide.

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