get_sleep_data

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description largely restates 'read-only' rather than adding new behavioral detail. Naming Garmin Connect as the source is mildly useful, but no data-freshness, missing-data, or timezone behavior is disclosed.

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?

It is short and front-loads the purpose, but the date format is stated twice in a single sentence ('cdate' format 'YYYY-MM-DD' and again 'Dates are YYYY-MM-DD'), which is pure redundancy in a one-line description.

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 read tool with full annotation coverage and an output schema, the description supplies what matters: the resource and the date format. Only the sibling disambiguation and date-semantics (night-of-sleep vs wake date) are missing.

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 0% and the single parameter 'cdate' has no schema description, so the description carries the burden — and it does specify the required YYYY-MM-DD format, which is exactly the missing information. It does not explain other aspects like whether the date means the sleep night's start or wake date.

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?

A concrete verb plus resource ('Return sleep data') with the date selector named, so the tool is identifiable at a glance. It does not distinguish itself from the closely related sibling get_sleep_stats_weekly (a weekly aggregate), which an agent may confuse with this single-date variant.

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 says nothing about when to use this versus siblings such as get_sleep_stats_weekly, get_user_summary, or get_daily_summaries. Usage is only implied by the parameter name, leaving the agent to infer the choice.

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