temperature_converter

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the conversion action and input format but does not disclose any side effects (e.g., whether it is a pure function, no external calls, or return value format). For a simple converter, this is minimal but acceptable; however, it lacks any statement about the nature of the operation beyond the conversion itself.

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 a single, efficient sentence that front-loads the purpose and then provides a compact input specification. Every element serves a purpose, with no filler or redundant information.

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 converter with no output schema, the description provides the essential information: what it does, the input parameters, and the allowed values. It does not explicitly describe the return format, but that is typically implied for converters. The low complexity means this is largely complete, though a brief note on return value would make it fully complete.

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 has no descriptions and no enums, so the description's hint that 'from' and 'to' accept 'c/f/k' adds critical meaning beyond the raw schema. It compensates for the 0% schema description coverage by clarifying the allowed values and their shorthand notation, which is essential for correct invocation.

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 converts temperature between Celsius, Fahrenheit, and Kelvin, with a specific verb ('convert') and resource (temperature). It naturally distinguishes itself from sibling converters (length, weight, etc.) by naming the exact domain, leaving no ambiguity about what it does.

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 for temperature conversion but does not explicitly state when to use it vs. alternatives or provide exclusions. However, the tool name and description make the intended context obvious among the sibling converters, so there is clear context without explicit guidance.

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