set_gateway_mode

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it's a system-wide setting affecting all zones and presets, and it explains the operational impact of each mode (e.g., 'away mode uses reduced temperatures'). However, it doesn't mention permissions, rate limits, or reversibility.

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?

Two sentences, front-loaded with the purpose and followed by explanatory details. Every sentence earns its place by clarifying scope and mode behaviors 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?

Given the tool's complexity (system-wide setting), no annotations, and no output schema, the description is fairly complete—it explains the effect of each mode. However, it lacks details on response format or error conditions, which would be helpful for a mutation tool.

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 documents the 'mode' parameter with enum values and descriptions. The description adds minimal value by restating the modes but doesn't provide additional syntax or format details beyond the schema.

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 verb ('Set') and resource ('gateway mode'), with specific options (home, away, vacation) that distinguish it from siblings like set_temperature or set_preset. It's not a tautology of the name.

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 by explaining what each mode does (e.g., 'Home mode uses normal schedules'), but it doesn't explicitly state when to use this tool versus alternatives like set_preset or set_regulation_mode, nor does it provide exclusions or prerequisites.

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