convert_units

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

No annotations provided; description only states functionality. It adds category support but does not disclose accepted unit formats, precision, or return value behavior, leaving significant gaps.

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?

Single concise sentence that is front-loaded and contains no 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?

For a simple converter with no output schema and no annotations, the description provides minimal context. It doesn't specify unit string formats, supported units per category, or error handling, making it insufficient for reliable invocation.

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 explain the 'value', 'from', or 'to' parameters or provide unit format examples, failing to compensate for the schema's lack of descriptions.

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?

Clear verb 'convert' with resource 'units' and explicitly lists supported categories (length, weight, temperature), distinguishing it from sibling converters like convert_currency and convert_timezone.

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 implies usage for length/weight/temperature conversions but does not explicitly state when to use or mention alternatives/exclusions. No guidance for non-supported conversion types.

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