conversion_fahrenheit_to_celsius

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

No annotations are provided, so the description carries the burden, but this is a pure, side-effect-free numeric conversion where little behavior needs disclosing. It does not mention rounding, precision, or how non-finite/out-of-range values are handled, leaving those traits undocumented.

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?

One short sentence that is fully front-loaded and contains zero filler. Nothing could be removed without losing meaning.

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 single-argument pure conversion with an output schema present, the description covers what is needed and return values need not be explained. It is nearly complete, missing only precision/rounding expectations.

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 description coverage is 0% and the single parameter is only named 'value' with type number, so the schema adds no units or format information. The description compensates contextually by implying the value is a Fahrenheit temperature, but adds no boundary or precision detail beyond that.

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 gives a specific verb ('Convert') and a precise directional resource ('temperature from Fahrenheit to Celsius'), which is exactly what distinguishes it from its inverse sibling conversion_celsius_to_fahrenheit. The purpose is unambiguous; it simply doesn't explicitly name alternatives.

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?

Usage is implied by the naming and the direction stated, so an agent can infer when to pick this over conversion_celsius_to_fahrenheit. However, it offers no explicit when-to-use guidance or edge-case conditions (e.g., negative values, precision).

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