convert_temperature

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

With no annotations, the description carries the full burden of behavioral disclosure. It lacks key details such as the fact that file parameters are always required (contradicting the 'direct input' suggestion), and it does not clarify what happens if both 'value' and 'file_content' are supplied. No return behavior or side effects are disclosed.

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 only two sentences long, front-loaded with the primary action and scope. It is concise and every word contributes meaning, though it could profitably include a bit more detail without losing compactness.

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 a simple temperature conversion purpose, the tool has six parameters and three required file-related fields. The description does not explain the relationship between file content and direct input, nor does it mention the mandatory file parameters. This creates a critical gap for correct invocation, especially with no output schema.

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 100%, so the input schema already documents all six parameters. The description adds minimal semantic value—merely restating that C and F are supported—which aligns with the baseline of 3 for complete schema coverage.

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 identifies a specific verb ('Convert') and resource ('temperature units'), distinguishing it from the sibling 'calculate' tool. It also names the supported scales (Celsius and Fahrenheit), leaving no doubt about the tool's core function.

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?

No guidance is provided for when to use this tool versus the sibling 'calculate'. The phrase 'based on file content or direct input' hints at usage contexts, but there are no explicit criteria or exclusions, leaving the agent to infer when conversion is appropriate.

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