get_sleep_summary_range

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 mentions that the tool makes one request per night internally and sets a maximum range, which are valuable behavioral details. However, it does not explicitly state that it is read-only or mention any authentication or rate-limit considerations, leaving some gaps.

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-organized with a clear initial statement, a usage note, and a separate paragraph for limitations. It is slightly repetitive in the first two sentences, but the overall structure is easy to follow and not excessively verbose.

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?

The description explains the purpose, usage, and constraints, and mentions that it returns the same metrics as get_sleep_summary, giving the agent a reasonable idea of the output. It does not fully enumerate the return schema, but the reference to a sibling tool and the list of example metrics make it sufficiently complete for decision-making.

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 description specifies the date format (YYYY-MM-DD) for both start_date and end_date, and clarifies that the range is inclusive. This adds meaningful information beyond the bare schema definition and ensures the agent can construct valid arguments.

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 that the tool retrieves lightweight sleep summaries for a range of dates, and explicitly distinguishes it from the sibling get_sleep_summary tool by saying it should be used when analyzing sleep trends over weeks or months. This gives the agent a precise understanding of the tool's function and its intended scope.

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 provides explicit guidance on when to use this tool instead of get_sleep_summary, and includes practical constraints such as the recommended range and maximum of 90 nights. It also discloses that it makes one request per night internally, which helps the agent anticipate performance implications.

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