convert_temperature

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions that conversion can be based on file content or direct input, but fails to explain that file_name, file_type, and file_content are required even for direct input, nor does it clarify how file content is processed or what happens with the data. This leaves significant behavioral ambiguity.

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 concise, consisting of two sentences that front-load the main action and then add unit support details. Every word contributes to understanding the tool's purpose, making it highly efficient.

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?

Despite having 6 parameters with no output schema and no annotations, the description is minimal. It does not explain the return format, error cases, why file parameters are required, or how the direct input mode interacts with the required file fields. This is insufficient for a tool with this complexity and dual-mode operation.

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 100% coverage for parameter descriptions, so the baseline is 3. The description adds semantic value by grouping parameters into two modes: file-based (file_name, file_type, file_content) and direct input (value, from_unit, to_unit). This extra context helps the agent understand how the parameters relate to each other beyond the schema.

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 uses a specific verb ('Convert') and resource ('temperature units'), and distinguishes itself from the sibling tool 'calculate' by focusing on temperature conversion. It also states the supported units (Celsius and Fahrenheit), making the tool's function clear and unambiguous.

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 when to use the tool ('Convert temperature units based on file content or direct input') but does not explicitly state when not to use it or mention alternatives like 'calculate'. It gives context about two modes but lacks clear usage boundaries or exclusions.

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