Start remote climate

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses concrete behavioral consequences: starting a hybrid runs the engine, so it must never be used in an enclosed space. It also clarifies the confirm flag's role as a preview-vs-send mechanism. This is high-value context.

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 compact and front-loaded: purpose first, then the critical safety warning, then confirmation usage. Every sentence earns its place without redundant detail.

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 output schema exists and parameters are fully described in the input schema, the description covers the remaining essential context: the preset behavior, the hybrid engine warning, and the confirm/preview semantics. Nothing critical is missing for correct invocation.

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 schema already fully documents confirm and temperature_celsius. The description adds useful context about the saved preset and preview behavior, but it does not need to compensate for missing parameter information.

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 states a specific action: "Start remote pre-conditioning with the saved preset (duration, defrosters, seats)." This is clearer than the title alone and distinguishes the tool from siblings like toyota_stop_climate and toyota_get_climate by naming exactly what starting climate does.

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?

It gives clear when-to-use guidance: "Only when the user explicitly asked; preview with confirm=false unless the user already confirmed." It also warns against use in enclosed spaces for hybrids. It does not explicitly name alternative tools, but the context and safety conditions are sufficient for selection.

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