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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds genuinely useful behavioral context the schema does not: results are derived from QUIKRETE No. 1101 yields and bag counts are rounded to whole bags, which tells the agent the numeric basis and rounding behavior of the output.

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?

A single dense sentence with zero filler, front-loaded on the verb and scope. Every clause (shapes, volume, waste allowance, bag counts, yield source) carries distinct information.

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?

Output schema exists so return values need not be re-explained, and annotations plus full schema coverage handle the mechanics. The description still supplies the calculation basis (QUIKRETE No. 1101) and shape coverage for an 11-parameter tool; only an explicit routing note toward generic volume tools is missing.

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 all 11 parameters (unit, count, waste, steps, rise, run, etc.) are already documented in structured data. The description mentions the shape families and waste allowance but adds no syntax, defaults, or unit detail beyond the schema; the baseline 3 applies.

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?

States a specific verb ('Computes') with a precise resource set: slab/footing/cylindrical-column/solid-step concrete volume, waste allowance, and whole 40/60/80 lb bag counts. It is immediately distinguishable from near-siblings like volume_calculator or gravel_calculator, which do not produce bag counts from a named mix yield.

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 shape list and concrete-specific scope imply when the tool applies (concrete pour estimates), but there is no explicit when-to-use statement or named alternative such as volume_calculator for non-concrete volumes. Usage is inferable but not stated.

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