get_sleep

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

Describes the return values, empty payload behavior, and subscription requirement. Annotations are absent, so description carries the full burden; it covers key behaviors but omits rate limits or data staleness beyond parameter-level sync note.

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 that front-load the core purpose and immediately follow with usage guidance and prerequisites, with no wasted words.

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 single-parameter tool with no output schema, the description thoroughly covers inputs, outputs, edge cases, and dependencies, providing complete context for an agent.

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 already provides 100% coverage for the date parameter, but the description adds valuable context about wake-up date keying and sync timing, enhancing the agent's understanding beyond the schema.

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?

Description clearly states the tool returns sleep time-series samples for one calendar day, listing the specific fields. It distinguishes itself from sibling tool list_sleep by specifying single-day focus.

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 instructs to use list_sleep for date range, and mentions the required API subscription with a 404 error if missing, providing clear usage boundaries.

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