list_sleep

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

Discloses it is read-only, returns 404 without subscription, omits nights without recorded sleep, and that future dates produce no entries. Covers all behavioral traits despite no annotations.

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 concise sentences with bullet-point-like format for fields. No wasted words, front-loaded with key 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?

Explains return fields in detail (timestamp, sleep stages, efficiency, score) and notes when entries are omitted. Complete for a list tool without output schema.

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?

Adds significant meaning beyond schema: specifies 'from' and 'to' as wake-up dates inclusive, notes silent omission for missing nights, and recommends ranges ≤30 days. Schema coverage is 100% but description still adds value.

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?

Clearly states it returns sleep time-series samples from the /247samples API for a date range, ordered chronologically. Distinguishes from sibling get_sleep for 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?

Explicitly mentions to use get_sleep for a single night, and notes requirement of Sleep API subscription. Provides clear context on when to use this tool.

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