Sleep trends

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds behavioral details: naps are counted but excluded from nightly averages, and the window range is 7-180 days. This goes beyond annotations to inform agents about data handling constraints.

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 two sentences: the first front-loads the main purpose and covered metrics, the second adds a crucial detail about nap handling. Every part is informative with no redundancy.

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 single optional parameter with default, the presence of an output schema, and annotations, the description covers all key aspects: metrics included, window range, and nap handling. No significant gaps remain.

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 has 0% description coverage, but the description compensates by explaining that the 'days' parameter defines the window length (7-180 days). This adds essential meaning beyond the schema's default value and type.

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 the tool retrieves sleep trends over a window (7-180 days) and lists specific metrics (hours slept, performance, efficiency, consistency, sleep debt, statistics, trend directions, unusual nights, nightly table). It distinguishes from sibling tools like get_sleep, get_sleeps, get_sleep_stream which are for single entries, multiple entries, or raw data.

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 usage for aggregated trend analysis over a period but does not explicitly state when to use this tool versus alternatives like get_sleep (single night) or compare_periods. The context is clear but lacks explicit when-not or exclusion statements.

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