set_seat_cool

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

With no annotations provided, the description must carry behavioral information. It discloses the auto-wake behavior ('auto-wakes if asleep'), which is valuable, but does not mention permissions, failure modes, or response format. This is partial transparency but not comprehensive.

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, well-structured sentence that front-loads the core action and includes beneficial level semantics and the auto-wake note. Every part contributes information without redundancy.

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 description covers the essential purpose, level range, and a notable behavioral trait. With 100% parameter description coverage and no output schema, it is sufficiently complete for a command tool, though it could mention what happens on failure or whether it returns a status. The auto-wake note adds useful context.

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 has 100% coverage for parameters, so the baseline is 3. The description adds semantic meaning by defining the level values (0=off, 1=low, 2=medium, 3=high), which is not fully explained in the schema. This enhances understanding beyond the schema's 'Cooling level 0-3'.

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's function: setting the cooling level for a specific seat, with explicit level mappings (0-3). This distinguishes it from sibling tools like set_seat_heat and specifics the resource (seat) and action (set cooling level).

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 provides clear context for when to use the tool (to set seat cooling levels) but does not explicitly mention alternatives or exclusion cases. It implies usage rather than giving explicit guidance about when not to use it or comparing with similar tools.

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