get_sleep

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

No annotations exist, so the description must cover behavioral traits. It implies a read operation and lists return fields, but does not explicitly state read-only, rate limits, or side effects. This is adequate but not fully transparent.

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 sentences: first states function with scope, second lists returned data and use case. No fluff or redundancy. Every sentence adds value.

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?

Given no output schema, the description explains return values adequately (duration, stages, efficiency, heart rate, HRV). It does not cover errors, pagination, or empty data, but for a simple date-range query, it is largely complete.

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 coverage is 100% with clear descriptions for start_date and end_date (format, defaults). The description's mention of 'date range' reinforces this but adds no new parameter meaning beyond the schema. Baseline score of 3 is appropriate.

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 the tool retrieves detailed sleep data for a date range and lists specific metrics (duration, stages, efficiency, heart rate, HRV). The verb 'Get' and resource 'sleep data' are specific, and the detail level distinguishes it from sibling tools like get_daily_sleep and get_sleep_time.

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 explicitly says 'Use this for analyzing sleep patterns and quality,' providing clear usage context. It does not mention when to avoid this tool or direct alternatives, but the sibling list implies different use cases, so it is still helpful.

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