calculate_paint_needed

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

With no annotations, the description must disclose behavior. It indicates it computes paint liters and recommends buying, implying a read-only calculator. It lacks details on side effects, error conditions, or the waste margin calculation, but the basic transparency is adequate.

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 three sentences, efficient and front-loaded with the purpose. It provides inputs, outputs, and a sibling suggestion without unnecessary words, though more structure (e.g., listing parameters) would improve clarity.

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 output schema exists, return values are covered. However, the description lacks explanation of the waste margin and does not differentiate from similar tools like calculate_paint_quantity, leaving gaps in completeness.

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 parameters are documented in the schema. However, the description mentions 'openings' as an input, which does not exist in the schema, and omits 'coverage'. This adds confusion and misrepresents the actual parameters.

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 'Compute paint quantity for walls including coats and waste margin', providing a specific verb and resource. It mentions usage for renovation budget, but does not explicitly differentiate from the sibling tool 'calculate_paint_quantity', which could cause ambiguity.

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 mentions 'Use for renovation budget' and suggests seeing list_bundles for related calculators, giving some context. However, it does not provide when to not use it or alternatives like calculate_paint_quantity, nor prerequisites (e.g., measuring wall area).

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