convert_units

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

With no annotations, the description must disclose behavior; it only states a cost and labels the tool as a converter. It does not explain what conversions are supported, how input/output is structured, or any side effects or requirements.

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 very short and includes a useful cost mention, but the phrase 'convert units — Converters tool' is redundant and contributes no real information. It is concise but not effectively structured.

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 tool with no annotations, no output schema, and a generic input schema, this description is far from complete. It leaves the agent guessing about accepted unit types, parameter format, and return values.

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?

Although the schema coverage is marked as 100%, the only parameter is a generic 'params' object with description 'Tool parameters as JSON object'. The description adds no detail about what keys or values the params object should contain, leaving actual semantics unresolved.

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 'convert units — Converters tool' essentially restates the tool name and offers no specific resource or scope. It does not distinguish this generic converter from sibling tools like temperature_all, speed_convert, or convert_currency.

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 guidance is given on when to use this tool versus alternatives. The description does not mention any exclusions, preferred cases, or relationships to the many specialized conversion tools available.

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