garmin_api_daily_summaries

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: raw JSON fields are not normalized, the original data envelope is included, and the range defaults to 7 days with a 31-day cap. It also implies no pagination by contrast with activity search. This is useful behavioral disclosure for an agent expecting structured output.

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 short and mostly front-loaded, with the range constraints following the core statement. However, the opening phrase 'User summary range response' is jargon-heavy and less immediately clear than a direct verb-resource statement. The activity-search parenthetical is relevant but slightly tangential; overall it earns its place with little 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?

An output schema exists, so return values need not be explained. But for a tool with many daily-summary siblings, the description fails to clarify what 'user summary' contains or how it differs from garmin_api_daily_summary. The range constraints and raw-data caveat are helpful, but the core question—what data is returned and when to prefer this over the singular sibling—is left under-specified.

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 schema does nothing to explain start_date and end_date beyond generic null defaults. The description compensates partially by stating the default range (7 days) and maximum range (31 days), but it does not specify date format, what happens if only one date is supplied, or whether both are optional in practice. Baseline 3 is appropriate because it adds some meaning but leaves gaps.

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 says 'User summary range response' but never uses a clear verb or states what data is summarized (e.g., daily wellness metrics). It implies a multi-day range, which loosely distinguishes it from the singular garmin_api_daily_summary sibling, but it does not explicitly name or differentiate from that sibling. The phrase 'including the original data envelope' is vague about the actual purpose.

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 only guidance is a date-range default (7 days) and a maximum (31 days). There is no explicit statement of when to use this tool versus garmin_api_daily_summary or other daily-summary siblings. The parenthetical '(activity search uses pagination)' references a sibling but does not tell the agent when to choose this tool over that one.

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