garmin_daily_summary

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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb 'Get' implies a read-only operation, and the output list communicates what is returned, but the description does not mention prerequisites such as login/session state, timezone semantics, or what happens when no data exists for the day.

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 efficient sentence that front-loads the tool's purpose and then lists the returned metrics. The biomarker list is long but compact and each item is relevant; the parameter guidance is appended clearly.

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?

The output schema covers return structure, and the description covers the day parameter format, so the core call is clear. However, the description omits usage routing among siblings and session prerequisites, which are relevant given the nearby garmin_login and garmin_resume_session tools.

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%, but the description adds the 'day: YYYY-MM-DD' format, giving the only parameter the meaning that the schema alone lacks. It does not specify allowed date ranges or timezone handling, but for a single simple parameter this is adequate.

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 uses a specific verb ('Get') and a clear resource ('one-day wellness summary'), then enumerates the covered biomarkers. This makes it immediately distinguishable from siblings like garmin_activities, garmin_resting_heart_rate, and garmin_summary_report.

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 phrase 'one-day' implies the tool is for a single-day summary, but the description gives no explicit when-to-use guidance or exclusions. It does not name any sibling alternative or explain when to prefer garmin_stats or garmin_summary_report instead.

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