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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes further by publishing the exact computation (cylinder volume, unit conversion from inches to feet, ÷27 for cubic yards, and a waste multiplier), which is real behavioral disclosure for a calculator beyond what annotations provide.

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 tight sentences with no filler: purpose, geometric differentiator, then the formula. Front-loaded and self-contained, though the formula line is dense and could have been broken out for readability.

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?

With no output schema, the description partly compensates by stating the formula's outputs (cubic feet and cubic yards), which is the core return value. It stops short of covering what bag_yield_cf produces — presumably bag counts — leaving that return dimension unaddressed for a 5-param 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?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by mapping parameters into the formula with units: diameter in inches divided by 24 to convert to feet, height in feet, count as a multiplier, and waste% added to the result. Only bag_yield_cf is left unexplained in the formula narrative.

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+resource (concrete volume for round columns, piers, tube forms/sonotubes) and explicitly differentiates its geometry from other concrete tools: 'Uses cylinder volume, which differs from slab math.' An agent can route this away from calc_concrete_slab, calc_concrete_footing, and calc_concrete_block without opening any schema.

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?

Usage is implied rather than stated: the round/tube geometry tells the agent this is the right tool for cylindrical pours, and the slab contrast hints at the alternative case. However, no sibling is named and there is no explicit 'use X instead when...' statement, so selection still requires inference.

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