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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that bulk density is editable and that output is in US short tons, which is useful context, but it omits anything about the density default-dependency or how results vary with unit selection.

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 front-loaded sentence with no filler; the primary action and output are stated first. It is dense but every clause (input shapes, depth, density) carries 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 format need not be explained, and the schema fully covers parameters. The description mentions the shape options, units, depth, and density, giving an agent enough to invoke it correctly, though it lacks guidance on when gravel versus adjacent calculators apply.

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 eight parameters are already documented in the schema, including depth units, area semantics, and density default. The description only restates a few of these (depth in inches, editable density) without adding syntax or format detail beyond the schema, so 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 (Calculate) and resource (gravel layer volume and US short tons), plus the three supported input modes (rectangle, circle, total area). It is clear what the tool does, though it does not explicitly differentiate itself from close siblings such as mulch_calculator or concrete_calculator, which an agent might confuse it with.

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 enumerates supported input shapes but gives no when-to-use guidance, prerequisites, or exclusions relative to the many other volume/cost calculators in the sibling list. Usage must be inferred entirely from the tool name and inputs.

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