garmin_get_sleep

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

Annotations declare readOnlyHint=true, which the description implicitly supports. The description adds constraints (max 31 days, default 7 days) and a data-source transparency note about Oura ring discrepancies. No contradictions.

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?

Three sentences efficiently convey purpose, output columns, range, and usage note. No extraneous content; 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?

With output schema present, the description covers the essential purpose, data shape (columns), and usage constraints. The only minor gap is lack of explicit return format (how rows are organized), but it is implied by 'per night'. Complete enough for a simple read tool.

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 definitions of start_date and end_date, including the night-ending interpretation. The description does not add significant meaning beyond the schema, only restating the range. 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 Garmin sleep data per night, specifies a table format with column details, and indicates a maximum 31-day range. This distinguishes it from sibling tools like garmin_get_daily_summary or garmin_get_activity_detail, which cover different data types.

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 explains the default range (last 7 days) and maximum (31 days), and includes a note about Oura ring as an alternative source for sleep data. However, it does not explicitly state when not to use this tool or recommend specific siblings for other purposes.

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