convert_units

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 does not state whether the operation is read-only, has side effects, or any other behavioral characteristics. The description only states the action without transparency about 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 short and front-loaded with the purpose. The second sentence about a contract reference may be of limited value to an agent but does not detract significantly. Overall, it is concise with no redundancy.

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 no output schema and no annotations, the description should provide sufficient context for correct invocation. It omits critical details such as exact unit strings, case sensitivity, handling of unsupported units, and the behavior of the precision parameter. The description is incomplete for an agent to use the tool reliably without additional information.

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?

The schema description coverage is 0%, so the description must compensate. It does hint at valid units (km/mi, kg/lb, °C/°F) which applies to from_unit and to_unit, but it does not explain the value, precision, or how units should be formatted. This is minimal compensation for the lack of schema documentation.

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 the tool's purpose: converting between specific unit pairs (km/mi, kg/lb, °C/°F). It uses a specific verb and resource, making the tool's function unambiguous and easily distinguished from the unrelated siblings.

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 (conversion) but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or conditions. Since siblings are unrelated, the context is clear, but no explicit when/when-not guidance is given.

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