convert_temperature

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

No annotations are available, so the description must carry full behavioral disclosure. It fails to explain why file parameters are required, how the tool handles missing optional parameters, or the output format. The mention of 'file content or direct input' is ambiguous.

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 very concise, with two sentences. However, it sacrifices necessary detail for brevity, making the tool harder to understand without additional context.

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?

Given the high parameter count (6) and lack of output schema, the description is insufficient. It does not explain how the different parameter groups work together, nor does it cover error conditions or result format.

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 coverage is 100%, but the description does not clarify the relationship between file parameters and direct input parameters. The description adds only the supported unit list, which is already in the schema enums.

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 name and description clearly indicate temperature conversion between Celsius and Fahrenheit. However, the required file parameters (file_name, file_type, file_content) are not explained, creating confusion about the tool's primary purpose.

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 on when to use this tool or how to choose between file-based and direct input modes. The required file parameters suggest a specific workflow, but alternatives are not mentioned.

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