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

With no annotations provided, the description must disclose behavioral traits itself. It mentions 'offline', indicating the tool does not require network access, which is a useful behavioral detail. However, it does not disclose what the output looks like, whether it is read-only, or any other side effects. For a simple conversion, this may be sufficient, but it is minimal.

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, concise sentence that immediately states the purpose. It is front-loaded with 'Temperature' and then 'Convert', providing clarity without any unnecessary words. 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 an output schema, but its content is unknown, and the description does not explain what the output will be. More critically, the input parameter 'q' is completely undocumented, and the description does not compensate for this. For an agent to call this tool correctly, it needs to know how to format the temperature input, which is missing. The description is incomplete for effective use.

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 input schema has a single parameter 'q' with no description, and schema coverage is 0%. The description fails to explain what 'q' should contain (e.g., the temperature value and its unit format). It only states the conversion capability, which does not clarify the parameter's expected format or structure, leaving the agent without essential information to correctly invoke the tool.

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 tool's function: converting temperature between Celsius, Fahrenheit, and Kelvin. It uses a specific verb ('Convert') and resource ('°C / °F / K'), and it distinguishes itself from the many other conversion tools in the sibling list (e.g., base64, base32) by focusing solely on temperature units.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention any exclusions or specific contexts. It only states the conversion capability, leaving the agent to infer that it should be used for temperature conversions. No alternative tools or conditions are referenced.

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