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

No annotations are provided, so the description carries the burden. It describes a pure calculation returning liters and recommended buying, implying no side effects, but does not explicitly state read-only or any behavioral traits. Adequate but not explicit.

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?

Three concise sentences with front-loaded main function, use case, inputs/outputs, and a pointer to related tools. No redundancy; every sentence contributes.

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 simple calculation tool with a complete schema, the description adds value by mentioning return values and use context. However, the inaccurate mention of 'openings' and omission of 'coverage' in the input list detract from 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% with clear parameter descriptions, but the description inaccurately lists 'openings' as an input (not in schema) and omits 'coverage', which is a parameter. This misalignment confuses the intended inputs and reduces clarity.

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 quantity for walls, including coats and waste margin, which is specific. However, it does not differentiate from the sibling 'calculate_paint_quantity', leaving ambiguity. The mention of 'renovation budget' provides context but not distinction.

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 suggests use for renovation budget and references 'list_bundles' for related calculators, but does not explicitly state when to use this tool instead of alternatives like 'calculate_paint_quantity'. The guidance is present but not thorough.

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