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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety and determinism are covered structurally. The description adds no behavioral context beyond those annotations, such as expected input precision, rounding behavior, or whether the conversion is purely numeric.

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 definition is extremely concise and front-loaded, with zero wasted words. However, it is arguably too compressed for a tool with three required parameters, so the brevity reflects under-specification rather than optimal conciseness.

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 the simple conversion operation and rich annotations, the definition still omits basic parameter context and does not clarify the expected input shape. For a tool with 0% schema description coverage, the description should do more to make the call semantics self-evident.

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 0%, and the description does not mention the value, from, or to parameters. While the schema's enums for from/to communicate the allowed units, the description does not compensate for the lack of parameter documentation or clarify that value is the numeric quantity to convert.

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 phrase 'Unit converter (weight)' does identify the resource domain as weight and distinguishes it from convert_length or convert_temperature. However, it is little more than a restatement of the tool name and title, with no explicit verb describing the conversion operation or its inputs.

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?

There is no guidance on when to use this tool versus sibling converters such as convert_length, convert_currency, or convert_temperature. The description does not mention any alternatives or exclusions, leaving usage entirely implicit.

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