convert_temperature

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

No annotations are provided, so the description must disclose behavioral traits. It does not disclose the return format, whether it modifies state, the relationship between file content and direct input, or any prerequisites. The phrase 'based on file content or direct input' is ambiguous without explaining precedence or requirements given the schema's required file parameters.

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 two sentences, front-loads the primary action, and contains no redundant or filler content. Every phrase adds information about the tool's scope.

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, no output schema, and no annotations. The description does not explain the required file parameters, how to invoke the tool correctly, or what the return value is, leaving significant gaps for a tool with this complexity.

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 baseline is 3. The description adds the concept of 'file content or direct input', which provides some context beyond the schema, but it does not clarify parameter combinations or precedence, so it does not meaningfully exceed the baseline.

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 verb 'convert' and the resource 'temperature units', specifically supporting Celsius and Fahrenheit. It distinguishes from the sibling tool 'calculate' by specifying the domain of temperature conversion.

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 this tool over 'calculate' or provide exclusions. It mentions 'based on file content or direct input' as usage context but lacks explicit guidance on choosing between the two input modes or alternative tools.

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