convert_temperature

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'based on file content or direct input' but does not explain how the file is processed, whether the file fields are mandatory, what the output format is, or any side effects. This leaves significant behavioral unknowns.

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 followed by a short clarification. Every word contributes to the core purpose, and it is front-loaded with the action. It is appropriately sized for a simple conversion tool.

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?

The tool has six parameters and two execution modes, yet the description gives no information about return values, input mode prerequisites, or edge cases. The absence of an output schema further increases the need for descriptive context, and this description falls short.

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 description coverage is 100%, so the baseline is 3. The description adds the concept of two input modes (file and direct) but does not clarify how the parameters interrelate (e.g., which fields to provide for direct input, or that file_content is injected). It provides marginal added value over 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 states a specific action ('Convert temperature units') and names the supported units (Celsius/Fahrenheit). This clearly distinguishes it from sibling tools like calculate or get_stock_price. The mention of 'file content or direct input' adds scope but doesn't detract from clarity.

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 provides no guidance on when to choose this tool over alternatives like calculate, nor does it explain when to use direct input versus file content. It simply describes the conversion function without any contextual cues or exclusions.

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