Sleep sensor stream

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

The description adds value beyond readOnlyHint by detailing the return data (heart rate, skin temperature, lowest heart rate, timestamp) and the behavior when the stream is unavailable. It also mentions the include_raw option. A slight deduction for not explicitly stating that it is a single-record operation (one sleep), but that is implied.

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 concise with no redundant sentences. It front-loads the core purpose, then provides sourcing, availability note, and optional parameter guidance in a logical order.

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 complexity (3 parameters, output schema exists), the description covers input sourcing, parameter behavior, return data summary, and an edge case (unavailable stream). It is complete and self-contained.

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?

Despite 0% schema description coverage, the description explains each parameter: sleep_id source, resolution_minutes as 'downsampled to resolution_minutes buckets', and include_raw as attaching the untouched payload. This fully compensates for the schema's lack of descriptions.

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 provides 'minute-level overnight sensor data for one sleep' with heart rate and skin temperature curves, plus stats. It also specifies how to obtain the sleep_id, distinguishing it from sibling tools like get_sleeps or get_daily_summary.

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 explicitly says 'Get the sleep_id from get_sleeps, get_daily_summary, or a recovery record' and notes that the stream may not be available for all accounts, with a clear note returned instead of an error. This provides when-to-use and when-not-to-use guidance.

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