sleep_summaries

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

No annotations are provided, so the description carries the full burden; it does reveal the default window of 14 days, which is genuine behavioral context the schema's null defaults do not convey. It does not state that the operation is read-only, how large a range is permitted, or what the return structure looks like.

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?

Two compact sentences with zero filler; the content scope is front-loaded and the default-range note follows. Nothing redundant.

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?

For a 2-param read tool with no output schema and no annotations, the essentials are present: what is returned, per what granularity, and the default window. Remaining gaps are date formatting and sibling disambiguation rather than core invocation blockers.

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 0% and both start_date/end_date are undescribed. The description partially compensates by disclosing what happens when they are omitted (last 14 days), but it never states expected date format (ISO?) or whether the bounds are inclusive.

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?

States a specific resource and granularity: nightly sleep summaries with duration, phases and sleep score. The verb is implicit (a read/list) but the scope is clear. It does not distinguish itself from the sibling sleep_day, so an agent cannot tell from the description which one to pick for a single night.

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 'Standard: letzte 14 Tage' clause implies the tool is used as a multi-night overview when no range is given, which is useful context. However, there is no explicit when-to-use, no exclusion, and no pointer to sleep_day as the single-day alternative.

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