garmin_heart_rate

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

The description mentions 'raw private heart-rate data' but does not elaborate on what 'raw' means (e.g., timestamps, intervals), whether data may be missing, or any rate limits. With no annotations, the description provides minimal behavioral 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?

A single, well-structured sentence that is front-loaded with the action and includes necessary format detail with no wasted 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 output schema exists, the description does not need to explain return values. However, it could be more complete by noting typical data granularity or error cases, but it is sufficient for a simple parameter tool.

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?

The schema has 0% description coverage, but the description clarifies the date format (YYYY-MM-DD) for the 'day' parameter, adding value beyond the schema definition.

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 it retrieves raw private heart-rate data for a specific date, with a required format hint (YYYY-MM-DD). This distinguishes it from sibling tools like garmin_hrv (HR variability) or garmin_sleep.

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?

No guidance on when to use this tool versus alternatives. For example, it doesn't explain when to prefer this over garmin_daily_stats or garmin_hrv, nor does it mention authentication prerequisites.

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