Get Current Eight Sleep Device

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

The readOnlyHint, idempotentHint, and destructiveHint annotations already cover the safety profile, so the description does not need to restate those. It adds the 'currently assigned' nuance and the allowed values, but it does not disclose additional behavior such as default user resolution or output shape; those are left to the schema and output schema.

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 that leads with the action and resource, followed by a compact parenthetical enumerating the possible values. There is no redundant wording or filler.

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 read-only lookup with rich annotations, optional parameters documented in the schema, and an output schema, the description is sufficient for an agent to invoke the tool correctly. No critical operational constraint or prerequisite is missing.

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 schema already documents user_id and privacy_mode with descriptions; response_format lacks a textual description but has a clear enum and default, so its semantics are still decipherable. The description itself adds no parameter-level meaning and does not fully compensate for the 67% schema description coverage, but the gap is minor.

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 uses a specific verb ('Return') and names the exact resource ('bed side currently assigned to the user') with the possible values (solo/left/right) explicitly listed. This clearly distinguishes it from the many get_* sibling tools, even though it does not name a sibling directly.

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 retrieving the current bed-side assignment, but it does not explicitly state when to use it versus alternatives like eight_sleep_set_side or eight_sleep_get_base. The usage context is inferable from the purpose statement, but no direct guidance is provided.

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