convert.unit

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details determinism, case-insensitivity, alias tolerance, return of exact result plus dimension, rejection of cross-dimension, and use of ground-truth factors. This fully informs the agent of the tool's behavior.

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 concise, using a few sentences that convey all necessary information without redundancy. Every sentence adds value: listing supported units, clarifying behavior, and noting limitations. No wasted words.

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?

Despite no output schema, the description explains return values (exact result + dimension). It covers all necessary aspects: supported unit types, case-insensitivity, alias handling, dimension constraints, and deterministic nature. Complete for a unit conversion tool.

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 coverage is 100% with basic descriptions for each parameter. The description adds meaning beyond the schema by explaining that units are case-insensitive with aliases, that conversion requires same dimensions, and that the return includes exact result and dimension. This enriches the agent's understanding.

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 it performs unit-of-measure conversion, lists supported dimensions (mass, length, volume, area, temperature), and explicitly differentiates itself from potential alternatives by emphasizing deterministic behavior and ground-truth factors. No sibling tool overlaps with this functionality.

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 provides clear guidance on when to use the tool for unit conversion within the same dimension, and explicitly states that cross-dimension conversions (kg→m) are rejected. It lacks explicit mention of when not to use, but the context of siblings and the tool's specific purpose makes usage clear.

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