convert_temperature

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

No annotations provided, so the description must compensate. It only states the conversion operation and return value, without detailing behavioral traits like side effects, permissions, or precision. This is insufficient for a tool with no annotations.

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?

Description is very concise (4 sentences) with no fluff. Each sentence serves a purpose: purpose, use cases, parameters, and related tools.

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 conversion tool with full schema and output schema, the description covers the main aspects: what it does, when to use it, and where to find related tools. Could mention precision or rounding but overall adequate.

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%, so baseline is 3. The description lists parameter names but adds no additional meaning beyond what the schema already provides.

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?

Clearly states the tool converts temperature between Celsius, Fahrenheit, and Kelvin, which is a specific verb+resource. It distinguishes from sibling conversion tools like convert_angle or convert_area.

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?

Provides some use contexts (cooking, weather, science) and mentions 'list_bundles' for related calculators, but does not explicitly advise when not to use this tool or differentiate from other conversion siblings like convert_cooking.

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