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

With no annotations, the description carries the burden of explaining behavior, and it does state the core conversion directions and material coverage. It does not disclose how qty, width_mm, and length_mm factor into the weight calculation, but for a non-mutating calculator tool the core behavior is adequately surfaced.

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 one compact sentence that front-loads the main purpose and enumerates supported materials. There is no redundant wording or filler.

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 seven parameters徒 with no annotations and no output schema, the description is too thin. It does not explain how mode selects the input direction, what the default material/dimensions are, or which parameters are needed for weight calculation, so an agent might invoke it incorrectly.

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 only 43%, leaving qty, material, width_mm, and length_mm undocumented in the schema. The description only mentions the material list and conversion modes indirectly, but does not compensate for the missing parameter semantics such as the role of dimensions and quantity in weight computation.

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 clearly states the tool's specific actions: converting sheet metal gauge to thickness in mm, thickness to gauge, and computing sheet weight for four named materials. It is specific about the resource and verb, though it does not explicitly distinguish itself from sibling tools like metal_weight_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 use is implied: an agent can infer this tool is for gauge/thickness conversion or sheet weight calculation. However, there is no explicit guidance on when to prefer this over alternatives such as metal_weight_calculator, nor any when-not-to-use conditions.

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