stop_steering_wheel_heater

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

No annotations are provided, so the description carries the full burden. It discloses the auto-wake behavior, which is a useful non-obvious trait, but it does not mention any potential side effects, error conditions, or the nature of the return value (e.g., whether it returns a command status).

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 immediately states the primary function, followed by a brief behavioral note. Every phrase earns its place with no extraneous content.

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 command tool with a clear action, 3 documented parameters, and no output schema, the description provides sufficient context. The auto-wake note is a valuable addition, and the absence of return-value details is acceptable given the lack of an output schema.

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 does not add any additional meaning about the parameters (vin, max_attempts, wait_for_completion), leaving the schema to fully document them.

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 action: 'Turns off the steering wheel heater' — a specific verb and resource. It also naturally distinguishes itself from the sibling tool 'start_steering_wheel_heater' by indicating the opposite action.

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?

Usage is implied: call this tool to turn off the steering wheel heater. The phrase 'auto-wakes if asleep' hints that no separate wake step is needed, providing some context, but it does not explicitly mention when to avoid using it or contrast with alternatives like 'set_temperatures'.

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