set_climate_keeper_mode

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

With no annotations, the description carries the full burden. It adds the useful behavioral note 'auto-wakes if asleep,' but does not disclose other potential side effects (e.g., battery impact in Camp mode) or the retry behavior tied to max_attempts. It provides some context, but not a complete picture.

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?

A single sentence with no filler. It front-loads the action, specifies all option values, and adds a key behavioral trait, earning every word.

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 setter with fully documented schema parameters, the description is mostly complete. It mentions the critical auto-wake behavior and all mode values. It does not explain wait_for_completion semantics or potential side effects, but these are minor gaps given the tool's low complexity and the schema's thoroughness.

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 all four parameters (vin, mode, max_attempts, wait_for_completion) already have descriptions. The tool description merely repeats the mode values already present in the schema, adding no new parameter semantics. Baseline 3 applies.

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 the specific verb 'Sets' with the clear resource 'Climate Keeper mode' and enumerates the mode values (0=Off, 1=Keep, 2=Dog, 3=Camp), making it easy to distinguish from sibling climate tools like start_climate or set_temperatures.

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 when-to-use guidance or alternatives are provided. The description only states what the tool does, without explaining when to choose this over start_climate, stop_climate, or other climate setters. The usage is implied but not explicitly guided.

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