get_sleep_summary

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds meaningful context with 'normalized' and 'stage totals,' hinting that sessions are reconciled across sources, but it does not explain the deduplicate/source_priority behavior or what normalization entails beyond that single word.

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 front-loaded sentence with no filler. It is efficient, but it is also arguably too terse given the number of undocumented parameters and the absence of an output schema.

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?

With no output schema, five parameters and 60% schema coverage, the description should say more about what 'stage totals' contains and how the date range maps to the days parameter. It is adequate to call the tool, but the agent lacks clarity on return shape and range semantics.

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 60%: source, deduplicate and source_priority are documented, while days and timezone are not. The phrase 'recent date range' loosely gestures at the days parameter, and 'normalized' gestures at deduplication, but neither adds real syntax or semantics beyond the schema, making 3 the appropriate baseline.

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 names a specific verb ('Return'), a specific resource ('sleep sessions and stage totals'), and a scope ('recent date range'). It clearly separates the tool from non-sleep siblings like get_activity_summary or get_recovery_summary, though it does not differentiate itself from get_daily_summary, which could plausibly also contain sleep 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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named among the many sibling summary tools. 'Recent date range' only faintly implies a boundary, and the agent must infer whether this tool or get_daily_summary is the right call.

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