calculate_paint_quantity

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

With no annotations, the description carries full transparency burden. It discloses that the tool returns liters and number of cans, which is good. However, it does not explain rounding or standard can sizes, but for a simple calculator this is acceptable.

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 two sentences, front-loaded with purpose, and includes inputs, outputs, and a pointer to bundles. No unnecessary information, earning the top score.

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 and presence of output schema implied, the description covers essentials: inputs and outputs. It lacks edge case handling (e.g., zero area) but is adequate for a paint calculator. Sibling list is large but tool is niche.

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 description coverage is 100%, so baseline is 3. The description lists the three inputs (surface m², coats, coverage) but adds no semantics beyond the schema, hence no extra value.

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 computes paint liters needed for a surface with chosen coats, indicating specific verb and resource. However, it does not explicitly differentiate from the similar sibling 'calculate_paint_needed', reducing clarity slightly.

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 says 'Use for painting projects', which gives clear context but lacks explicit guidance on when not to use it or alternatives. The pointer to 'list_bundles' for related calculators is helpful but does not name specific alternatives.

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