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

With no annotations, the description carries the full burden, and it does reasonably well: it reveals the calculation method (D×R×C adjusted by sticker thickness and fill factor), the typical fill-factor range, and the m³-to-board-foot conversion. It does not describe the exact return shape or edge cases, but the core behavior is transparent.

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 description is compact and front-loaded: purpose, formula, parameter meanings, and output conversion all fit in two sentences with no redundant filler. Every phrase contributes.

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?

Given no output schema and no annotations, the description is mostly adequate—it gives the formula, variable meanings for t/s/f, and output units—but it does not define D/R/C or describe the returned data shape, leaving noticeable context gaps for an agent invoking the 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 adds meaning by mapping t, s, and f to board thickness, sticker thickness, and fill factor and by giving a typical fill-factor range, but it leaves D, R, C unmapped to the schema's length_m, width_m, and height_m, so it stays at baseline.

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 states a clear function: compute kiln charge capacity / wood volume per batch, backed by an explicit formula and output units. It is not a tautology and goes beyond the name, though it doesn't explicitly differentiate itself from sibling calculators such as board_feet_calculator.

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 intended context is implied by 'Kiln charge capacity' and the formula, so an agent can infer when to use it. However, there is no explicit statement of when to use this tool instead of the many related lumber/volume calculators, nor any exclusions or prerequisites.

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