garmin_get_sleep

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the specific output (sleep stages and metrics) but does not disclose behaviors like refresh semantics or whether include_raw affects the response. With annotations present, the added value is modest, so a 3 is appropriate.

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?

The description is a single sentence that is front-loaded with the action and resource. It is concise and every word contributes meaning, with no redundancy or filler.

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?

While the output schema covers return values, the description fails to explain two of the three parameters, particularly the boolean flags. For a tool with multiple parameters and low schema coverage, this is a significant gap that hinders autonomous selection and invocation. The description is not complete enough for an agent to use it correctly without additional assumptions.

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 description coverage is 0%, so the description must compensate. It explains 'day' as a YYYY-MM-DD date, but 'refresh' and 'include_raw' are completely unexplained. This leaves the agent without critical information on how these boolean flags alter behavior.

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 action (Get), the resource (sleep stages and available sleep metrics), and the scope (one YYYY-MM-DD date). This differentiates it from sibling tools like garmin_get_activity or garmin_get_body_metrics, which focus on other 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 implies usage for retrieving sleep data for a single date, which is clear context. However, it does not explicitly mention alternatives or when not to use this tool. The clarity of the purpose provides sufficient guidance for most cases.

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