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

With no annotations, the description carries the full behavioral burden. It usefully discloses the unit definitions and optional species/moisture-based weight estimate, but it does not explain what the tool returns, how a target unit is selected, or why 'solid m3' appears in the description but not in the schema's 'from' enum.

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 sentence with no filler: it front-loads the action, captures the unit scope, and mentions the optional weight estimate. Every clause contributes 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?

There is no output schema and no annotations, so the description alone must clarify output behavior. It never states what a successful result looks like, how the output unit is chosen, or that the tool returns all conversions. The mismatch between 'solid m3' in the description and its absence from the input enum further weakens completeness.

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 83%, so parameters are already well-documented. The description adds context about the unit families and weight estimate, but largely restates what the schema already says without adding deeper parameter meaning.

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 a specific verb ('Convert') and resource ('firewood volume'), lists the supported units, and adds the optional weight-estimate capability. This clearly distinguishes the tool from siblings such as timber_unit_converter or 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 firewood-specific domain and listed units imply when the tool should be used, and the tool is clearly set apart by content. However, it never explicitly says when not to use it, nor does it name alternatives like timber_unit_converter for generic conversions.

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