Set Eight Sleep Away Mode

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

Annotations already indicate mutability, side effects, idempotency, and non-destructiveness. The description adds the EIGHT_SLEEP_ALLOW_MUTATIONS requirement, which is a useful behavioral constraint not covered by annotations. No contradiction.

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 extremely concise (two short sentences) and front-loads the main purpose. Every sentence is necessary and adds value.

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 has three parameters and an output schema, the description omits critical details about parameters (e.g., what 'user_id' does) and does not utilize the output schema to explain return behavior. It is incomplete for informed usage.

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 0%, and the description does not explain the meaning or allowed values of 'is_away', 'user_id', or 'response_format'. The description only hints at the purpose of 'is_away' implicitly but lacks explicit parameter documentation.

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 it 'Toggle away mode', which is a specific verb+resource. It distinguishes from sibling tools like set_side and set_temperature by focusing on away mode.

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 a critical prerequisite: 'Requires EIGHT_SLEEP_ALLOW_MUTATIONS=true'. However, it does not explicitly indicate when to use this tool versus alternatives or exclude certain scenarios.

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