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

The description communicates the core conversion behavior and category scope but adds little behavioral detail beyond the annotations. Important caveats such as 'temperature units aren't validated — a typo returns garbage' and 'data units are binary' live in the schema rather than the description. There is no contradiction with readOnlyHint=false or destructiveHint=false.

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 a single, front-loaded sentence with no filler beyond the redundant 'Unit Converter —' prefix, which repeats the title. Overall it is compact and scannable.

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?

For a simple four-parameter conversion tool with fully described schema fields, the description supplies enough scope to select the tool correctly. The only minor gap is that no output format is described, though the expected result of a unit conversion is fairly predictable.

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%, and the schema thoroughly documents value, from, to, and category, including snake_case naming, binary data units, and temperature restrictions. The description only adds high-level category context, so it does not meaningfully extend the schema's parameter guidance.

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 specific operation, 'Convert between units of measurement', and enumerates the supported categories: length, weight, temperature, volume, area, speed, time, and data sizes. This clearly distinguishes it from the many convert_file/convert_document/convert_data siblings.

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 clearly frames when to use the tool: whenever a unit conversion between named measurement categories is needed. It does not explicitly name alternatives or exclusions, but no sibling tool appears to cover unit conversion, so the context is sufficient.

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