Get Garmin daily summary

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 'Garmin Connect China' region context, which is useful but not covered by annotations. It does not describe return format, pagination, or any limitations beyond the date parameter, but given annotations, this is adequate for a read-only simple tool.

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, direct sentence that fully conveys its purpose without any filler. The core resource and date format are front-loaded, and there is zero wasted wording. This is an ideal length for a simple tool with one parameter.

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 the output schema exists (so return values are documented elsewhere) and annotations cover safety, the description is nearly complete for a simple read operation. However, it lacks usage guidance distinguishing it from siblings, and does not hint at what the 'summary' includes (e.g., activity, sleep, HRV). This leaves an agent uncertain about when to choose this over specific metric tools, making it slightly incomplete.

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% — the 'date' parameter has no description. The description partially compensates by specifying the format 'YYYY-MM-DD', which is a useful hint beyond the plain 'string' type. However, it does not explain the expected date range, timezone implications, or that the date must be a valid calendar date. With a single parameter, the compensation is minimal.

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 states the verb 'Get' and a specific resource: 'Garmin Connect China daily wellness and activity summary' with a date parameter. It clearly indicates a composite summary, distinguishing it from sibling tools like get_sleep or get_heart_rate which target specific metrics. However, it does not explicitly name the siblings it is not, leaving the distinction implicit.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this tool is the broad daily summary while get_sleep, get_heart_rate etc. are for specific metrics, nor does it state any prerequisites or exclusions. An agent would have to infer usage from the title and sibling names.

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