Eight Sleep Sleep Efficiency

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

The description adds substantial behavioral detail beyond annotations: it reuses existing API payload with no extra calls, explains graceful degradation when data is missing, and states that natural-language observations are only included when supported by data. This provides excellent transparency.

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 well-structured and informative, with a version header, clear listing of computed metrics, and edge-case handling. It is slightly verbose but every sentence adds value. Minor improvements could combine some details.

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?

Without an output schema, the description fully explains the return structure: nights_analyzed, mean/median/min/max, per_night array, efficiency bands, and observations. It also covers edge cases like missing data. The tool is self-contained and clearly documented.

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 input schema covers all three parameters with descriptions and defaults (nights, timezone, response_format). The description adds little beyond stating the default of 7 nights, so it does not significantly enhance parameter understanding. Baseline of 3 is appropriate given high schema coverage.

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 is a sleep efficiency calculator that computes a specific set of metrics (time_in_bed, time_asleep, efficiency_pct, efficiency_band) and returns detailed analysis. However, it does not explicitly differentiate from sibling tools like eight_sleep_nightly_summary or eight_sleep_get_trends.

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 explains what the tool does but provides no explicit guidance on when to use it vs. alternatives. The usage context is implied (analyzing sleep efficiency over recent nights) but lacks clear conditions or exclusions.

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