Set Eight Sleep Side On/Off

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

Annotations already indicate this is a write (readOnlyHint=false), idempotent, and non-destructive. The description adds value beyond annotations by disclosing the mutation gate requiring explicit user intent and an environment flag, which is meaningful behavioral context the agent needs before invoking.

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, both essential: the first states the action, the second states the gating requirement. No filler, front-loaded action first.

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 core action and gate are fully conveyed, and the output schema plus annotations cover the return contract and safety profile. Minor gaps remain: the purpose of user_id and response_format isn't clarified, and behavior when the gate fails isn't described, but these are secondary for a simple boolean toggle 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 coverage is 50%, with user_id and response_format lacking descriptions in the schema. The tool description reinforces the explicit_user_intent gate but adds no new meaning for is_on, user_id, or response_format beyond what the schema already provides, so it doesn't compensate for the undocumented parameters.

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 verb and resource: 'Turn the user's bed side on or off.' This is unambiguous and distinct from sibling tools like eight_sleep_set_temperature or eight_sleep_set_away_mode, though it doesn't explicitly name a sibling for differentiation.

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 invocation context: the tool is gated by explicit_user_intent=true and EIGHT_SLEEP_ALLOW_MUTATIONS=true, telling the agent the precondition for calling it. It doesn't mention exclusions or alternatives, but the gate condition is actionable guidance.

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