Get Eight Sleep Temperature

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds what data is returned but does not elaborate on behavioral aspects like permissions, rate limits, or side-specific handling. The description is adequate but not rich.

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?

Single sentence, 12 words, front-loaded with the purpose. Every word earns its place; no fluff. Ideal for quick understanding.

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 presence of an output schema and annotations, the description is brief but covers the main returns. However, it lacks context on units, side-specific details, or relation to scheduled levels, which might be needed for correct invocation.

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 67% and the tool description does not add parameter-level details. It adds no value beyond the schema, which is already fairly descriptive for user_id and privacy_mode but missing for response_format. Baseline 3 is appropriate.

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 returns current heating level, smart-schedule levels, and side on/off state, using a specific verb 'Return'. It distinguishes from sibling tools like eight_sleep_set_temperature (write) and eight_sleep_temperature_trend (trends), but could be slightly more precise about the scope.

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?

No explicit guidance on when to use this tool vs alternatives. While the readOnlyHint annotation and sibling context imply it's for reading temperature data, the description itself does not provide usage context or exclusions.

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