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

No annotations are provided, so the description must fully disclose behavior. It states that it computes and returns grout kg, but omits important details such as whether the tool is read-only, idempotent, or any error conditions.

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 concise at three sentences, with a clear first sentence for purpose. However, it could be better structured with bullet points or a more explicit list of inputs and output.

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 that the tool has four parameters (two required) and an output schema exists, the description covers the main purpose, typical use (renovation budget), and points to related tools. It is adequate for a simple computation tool.

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 describes all parameters with 100% coverage. The description only lists three inputs ('surface m², tile size, joint width') but omits the depth_mm parameter. It adds minimal new meaning beyond the schema.

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 grout quantity for tiling jobs with a specific verb and resource. However, it does not differentiate from the sibling tool calculate_tile_quantity, which could cause confusion.

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 mentions using it for renovation budget and points to list_bundles for related calculators, but it does not explicitly state when to use this tool versus alternatives like calculate_tile_quantity.

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