convert_temperature

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world, so safety behavior is covered. The description adds the supported unit set but does not mention precision, accepted input formats, error behavior, or return shape.

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 compact sentence with the key operation and units front-loaded. It contains no filler or redundant restatement.

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?

For a simple conversion tool with annotations covering safety and no output schema, the description is minimally adequate. However, with 0% schema coverage it should do more to clarify the exact unit strings accepted by from and to and the expected result form.

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 0%, so the description must compensate for three undocumented parameters. It mentions C/F/K units, which maps loosely to from and to, but does not specify parameter names, accepted string forms, case sensitivity, or what value represents beyond the obvious number type.

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 verb and resource: converting temperature units, with the supported unit set C/F/K. It is clear what the tool does, though it does not distinguish itself from the sibling temperature_convert tool.

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 it should be used for temperature conversion but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not explain why an agent should choose this over the sibling temperature_convert.

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