convert

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

Description discloses return value shape (converted value, conversion factor, or structured error for incompatible units), which is helpful. No annotations are present, so the description carries the burden. It does not mention idempotency or side effects, but for a conversion tool, the behavior is well captured.

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?

Two sentences with no wasted words. The key information (what it does, what it returns) is front-loaded.

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 complexity of unit conversions (multiple unit systems, compound units), the description is too sparse. Parameter details are missing, and there is no cross-reference to sibling tools that might help with unit discovery. The output schema may exist but is not available to evaluate; still, the description does not fully compensate for the lack of schema descriptions.

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?

Input schema has 0% description coverage, so the description must compensate. However, the description does not explain what from_unit and to_unit expect (e.g., string format, allowed values). It only says 'unit' without details, leaving the agent guessing about accepted unit syntax.

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?

Description clearly states the verb ('convert') and resource ('value from one unit to another'), and distinguishes from siblings like check_compatibility (which only checks) and list_compatible_units (which lists).

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?

No explicit when-to-use or not-to-use advice, but the tool's purpose is clear enough that it is the main conversion tool. Sibling tools are conceptually distinct, but no guidance is given on when to choose convert over check_compatibility or others.

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