Get Eight Sleep Adjustable Base

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces this by saying 'Return' rather than 'change' and adds the concrete state fields returned. It does not describe side effects because there are none.

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?

A single sentence front-l-loads the action and the exact payload with zero redundancy. Every word contributes 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?

The tool has no required parameters, annotations declare it safe and idempotent, and an output schema exists, so the absence of return-type detail in the description is acceptable. The only minor gap is no mention of how 'preset' is represented, which the output schema covers.

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?

The description does not mention parameters, but the schema provides clear descriptions for user_id (defaults to authenticated user), privacy_mode (override with default), and response_format (default markdown). Since the schema is informative, the description adds no extra meaning but the agent can nevertheless invoke the tool correctly.

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 opens with the verb 'Return' and names the specific resource, 'adjustable-base state', plus the exact fields delivered ('leg angle, torso angle and preset'). This clearly distinguishes it from sibling getters like eight_sleep_get_temperature and eight_sleep_get_current_device.

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 does not explicitly state when to prefer this over alternatives, but the resource name and description make the use case obvious: retrieve the current adjustable-base configuration. There are no overlapping sibling tools for this resource, so an explicit exclusion is not strictly necessary.

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