Garmin Daily Heart Rate

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds a disclaimer 'Not medical advice' but does not elaborate on behavioral traits like rate limits or authentication needs. It provides marginal value beyond the annotations.

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 extremely concise: a single sentence defining the purpose plus a one-phrase disclaimer. It is front-loaded with the action verb and resource, with no unnecessary words.

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 tool's simplicity, the presence of annotations (readOnly, idempotent), and an output schema, the description is largely adequate. It explains what data is retrieved (samples and resting context). However, it omits usage context like authentication requirements, which are implicit from sibling 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?

With schema description coverage at 67% (date and privacy_mode described in schema, response_format lacking), the description does not add any parameter-level meaning beyond what the schema provides. The description mentions 'heart-rate samples and resting heart-rate context' but does not map to individual parameters.

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 clearly states the verb 'Get' and the resource 'daily heart-rate samples and resting heart-rate context for a date', which precisely defines the tool's function. It distinguishes itself from sibling tools like garmin_get_hrv_day or garmin_get_stress_day by focusing on heart rate data.

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 such as garmin_get_hrv_day or garmin_get_stress_day. It lacks explicit context for when to choose this tool, such as prerequisites or exclusions.

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