get_sleep_data

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

With no annotations, the description carries the behavioral disclosure burden. It discloses a useful nuance: the date parameter is 'the date you woke up on,' and the default is today, which clarifies how sleep sessions are attributed across nights. However, it does not mention read-only guarantees, error behavior, or data-availability caveats, leaving the transparency incomplete for an unannotated tool.

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 short, front-loaded with the tool's purpose, and the parameter documentation is formatted clearly beneath it. There is no redundant prose; every sentence adds information.

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 tool has only one optional parameter and an output schema, so the description needs to cover little beyond parameter semantics and core outcome; both are present. A point is withheld because it does not clarify how this tool relates to the overlapping get_daily_summary sibling or what happens when no sleep data exists.

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 provides only a nullable string with a null default, but the description fully specifies the accepted formats: YYYY-MM-DD, 'today', 'yesterday', offsets like '-3', and the default of today. This completely compensates for the 0% schema description coverage.

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 identifies the output resource: 'Sleep stages and sleep score for a night.' It lacks an explicit verb such as 'retrieves' or 'returns,' and it does not distinguish itself from siblings like get_daily_summary, but the resource is specific enough that an agent can infer the core purpose.

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?

No guidance is provided for when to choose this tool over sibling tools such as get_daily_summary or get_activities. The only usage-related content is the date parameter explanation, which is parameter semantics rather than tool-selection guidance.

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