set_temperatures

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the auto-wake behavior, which is a valuable trait not evident from the schema. However, it doesn't specify whether the command turns on the climate system, requires the car to be awake, or any failure/return behavior, leaving gaps.

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, front-loaded sentence that states the action and key behavior with no filler. Every word earns its place, making it highly efficient.

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 is a simple setter with four parameters and no output schema, but the description is minimal. It does not clarify whether climate control must be active or how this relates to start_climate, though the auto-wake note helps. The schema covers parameter details, but the description leaves some operational context uncertain.

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's temperature range (15-28°C) duplicates what's already in the schema's min/max, and it adds no additional parameter semantics for vin, max_attempts, or wait_for_completion.

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 uses a specific verb+resource ('Sets the cabin temperature') with an explicit temperature range (15-28°C), clearly distinguishing it from sibling climate tools like start_climate or set_seat_heat. The auto-wake note adds behavioral context but doesn't obscure the core 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?

The description implies usage for setting the cabin target temperature but provides no explicit when-to-use or alternatives. The 'auto-wakes if asleep' note gives a usage condition (works when the vehicle is asleep), but it doesn't compare against related climate controls like start_climate or stop_climate.

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