Set Eight Sleep Away Mode

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

Annotations already establish this is a non-read-only, idempotent, non-destructive mutation. The description adds a meaningful behavioral constraint: the mutation is gated by explicit user intent and an environment flag. It does not explain side effects of away mode, but the idempotent and non-destructive hints cover the main safety profile.

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 two short sentences with no filler. The core action is front-loaded, and the gating condition immediately follows. Every word contributes useful information.

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 boolean setter with an output schema, annotations, and a clear required parameter, the description is mostly sufficient. The main missing context is a brief note on what away mode affects or when user_id would be needed, but the required call path is clear.

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?

With schema description coverage at 25%, the description partially compensates: 'away mode' clarifies what the is_away boolean controls, and the gating line adds meaning to explicit_user_intent. However, user_id and response_format receive no additional semantic guidance beyond their names and schema definitions, so the compensation is incomplete.

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 ('Toggle') and resource ('away mode'), which clearly identifies what the tool does and distinguishes it from sibling setters like set_temperature and set_side. However, 'Toggle' is slightly imprecise because the actual parameter is an explicit boolean setter, not a state-flipping toggle.

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 the tool is for enabling or disabling away mode and gives a hard precondition: explicit_user_intent: true and EIGHT_SLEEP_ALLOW_MUTATIONS=true. It does not explicitly say when to prefer this tool over alternatives or when not to use it, so usage guidance is mostly implied rather than stated.

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