get_sleep_stats_weekly

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds useful context: Garmin Connect as the source and YYYY-MM-DD date format. However, it doesn't mention data freshness, pagination, or any constraints on the weekly aggregation.

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?

One compact sentence plus a brief parenthetical. The core purpose is front-loaded, and every phrase contributes information without waste.

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?

Because an output schema exists, return values needn't be explained, and annotations cover safety. Still, the missing usage guidance and the unexplained `weeks` parameter mean an agent cannot confidently determine the time window behavior from the description alone.

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 neither `end` nor `weeks` is documented in the schema. The description only implicitly gives the `end` date format; the `weeks` parameter (default 52) and its relationship to `end` are entirely unexplained, leaving a significant gap.

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?

States a specific verb ('Return') and resource ('weekly sleep statistics') and even lists the returned fields (overallStats + per-week values). It does not differentiate from the sibling get_sleep_data, which likely covers daily sleep, so sibling distinction is missing.

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 gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer from the name that this is for weekly aggregates rather than daily data or other sleep endpoints.

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