convert_temperature

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a converted temperature, implying a read-only operation with no side effects. This is sufficient for a simple conversion tool, though it could mention handling of invalid inputs or edge cases.

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: the first states core functionality, the second adds use cases and a pointer to related tools. It is concise, front-loaded, and contains no redundant information.

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 simple nature of the tool (three parameters, output schema present), the description covers all essential aspects: purpose, inputs, outputs, use cases, and a reference to related bundles. It is complete for the intended 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 schema covers all parameters with descriptions and enums, so baseline is 3. The description merely lists parameter names ('value, from, to') without adding significant meaning beyond what the schema already provides.

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 converts temperature between Celsius, Fahrenheit, and Kelvin, specifying the verb 'Convert' and the resource 'temperature'. It distinguishes from sibling conversion tools by naming specific units and providing use cases (cooking, weather, science).

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 gives clear context for when to use the tool (cooking, weather, science) and references list_bundles for related calculators. However, it does not explicitly state when not to use it or name alternatives, which would strengthen guidance.

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