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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral content beyond that: the exact cubic-yard formula, the inch-to-foot conversion convention, and the waste multiplier applied to the result. It does not explain the role of bag_yield_cf or what the response contains, but the core computation is fully disclosed.

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?

Two compact sentences with zero filler; the scope and formula are front-loaded and every clause carries information an agent needs. No repetition of the title or restating of field names without purpose.

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 read-only, five-optional-parameter calculator with no output schema, the description gives the scope, unit conventions, and formula, which is nearly enough to call it correctly. The gap is that the output contents (notably any bag count derived from bag_yield_cf) go unexplained, and no output schema compensates.

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 the baseline is 3. The description reinforces the unit semantics of width_in and length_ft and shows how waste_pct enters the formula, but it says nothing about bag_yield_cf, the fifth parameter, so it adds only marginal meaning over 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?

States a specific verb (compute volume) and a precisely scoped resource (continuous trench/wall footings), which cleanly separates it from siblings like calc_concrete_slab and calc_concrete_column. The unit convention (width in inches, length along the full perimeter) further pins down what is being computed.

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 scope phrase 'continuous trench/wall footings' implies when to use it versus the slab/column/block calculators, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Adequate but leaves the routing inference to the agent.

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