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

With no annotations, the description carries the full burden. It discloses the outputs (total tiles, boxes, cost) and mentions waste percentage, but does not explain key behaviors like rounding up boxes, unit conversion (ft vs inches), or how waste is applied. This is adequate but incomplete for a calculator with hidden assumptions.

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 a single sentence that is front-loaded with the tool's primary action. It provides all key information without unnecessary words, making it highly concise and scannable.

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 7-parameter calculator with no output schema, the description should explain more than it does. It lists the outputs (tiles, boxes, cost) and inputs, but does not cover boundary cases, rounding rules, or unit conversion details. It is minimally complete for a simple calculator, but leaves important gaps.

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 0%, so the description must compensate for all 7 parameters. It mentions room size and tile dimensions but does not explicitly name or explain tilesPerBox and pricePerBox, nor does it state the units (e.g., feet vs inches) beyond what property names already imply. The description adds insufficient parameter detail.

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 uses a specific verb ('Calculate') and resource ('floor or wall tiles'), clearly stating the scope ('how many you need'). It distinguishes this from sibling calculators like concrete_calculator and flooring_calculator by focusing on tile-specific inputs and outputs.

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 you need tile quantity') and lists the required inputs, but provides no explicit exclusions or comparisons to alternatives. The context is clear but not differentiated from similar calculators.

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