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

Annotations already cover the read-only, closed-world profile, so the description's added value is in disclosing the computation basis (USG published coverage) and the rounding rules ('rounded up' for pails and rolls). It does not mention edge cases such as zero area or how defaults are applied.

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 purpose sentence is front-loaded and the formula block is terse and directly tied to the outputs. Nothing is repetitive filler; each clause maps to a returned quantity or a parameter.

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 carries the return-value burden and does so by enumerating gallons, pails, tape feet and rolls. For a deterministic six-optional-parameter calculator this is nearly sufficient, lacking only note on default behavior when area is omitted.

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 baseline is 3; the description earns above baseline by showing exactly how the coverage and tape-per-1,000 parameters enter the formulas and by noting the waste multiplier applies to both materials. It does not explain units conversions or what happens if coverage values conflict with the defaults.

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 names the exact resource (ready-mix joint compound, pails, paper tape) and the output units (gallons, pails, rolls, ft), which cleanly separates it from sheet-counting siblings like calc_drywall. It never explicitly names a sibling to disambiguate against, which keeps it from a 5.

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 by 'How much drywall mud and tape to buy ... for your square footage of drywall,' but there is no explicit when-to-use statement, no prerequisite (e.g. tape joint type, coat count), and no pointer telling the agent to use calc_drywall for board count instead.

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