calculate_water_heater_size

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

No annotations are provided, so the description must disclose behavioral traits. However, it only states the calculation purpose without mentioning the algorithm, units (e.g., gallons/liters), output format, or any assumptions (e.g., standard usage rates). This leaves the agent with insufficient context about the tool's behavior.

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 with zero wasted words. The first sentence front-loads the purpose, and the second provides a navigational hint. 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 the tool's simplicity (two parameters, output schema present), the description is complete enough. The output schema likely documents the return value, so the description does not need to explain it. The reference to list_bundles adds useful context about related calculators.

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?

The input schema already provides descriptions for both parameters (household_size, usage) with detailed explanations (e.g., usage levels with L/person). The description does not add additional meaning beyond the schema, so a baseline of 3 is appropriate given the high schema coverage (100%).

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 function: 'Calculate recommended water heater tank size for a household.' It uses a specific verb ('calculate') and resource ('water heater tank size'), and distinguishes itself from sibling calculators by focusing on household context and the specific domain of water heating.

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 through its name and purpose, and references list_bundles for related plumbing calculators, but does not provide explicit guidance on when to use this tool over alternatives or conditions to avoid.

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