Get Garmin stress

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real behavioral detail beyond them — that today's row is partial, the default window, and the 28-day per-call ceiling. It doesn't mention pagination or rate limits, but for a read-only daily-series tool this is solid added context.

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 compact sentences, front-loaded with the resource and its metric definitions, then the partial-day caveat, then the window limits. No filler or redundancy; every clause carries information an agent needs.

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?

There is no output schema, but the description effectively documents the return shape (per-day average stress plus minutes in each of four bands) along with the partial-day caveat for today. Combined with fully documented date parameters, an agent has everything needed to call it correctly.

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 100%, so both date parameters are already fully documented in the schema, including defaults and the time-zone note. The description restates the 7-day default and 28-day limit but adds no new syntax or format meaning beyond the schema, so baseline 3 applies.

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+resource ('All-day stress per day over a date range') and immediately defines the returned metrics with their value ranges (average 0–100, minutes in rest/low/medium/high buckets). This is clearly distinguishable from siblings like garmin_get_hrv, garmin_get_sleep or garmin_get_body_battery without opening any schema.

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?

Gives concrete operational context: defaults to the last 7 days and a hard cap of 28 days per call, which tells an agent how to scope requests. It does not name an alternative tool or state when to prefer a different stress/wellness endpoint, so it stops short of full when/when-not routing.

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