garmin_health

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

No annotations provided, so description must cover behavior. It details what each metric returns but omits potential issues like data unavailability for future dates, rate limits, or authentication requirements. Partial transparency.

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?

Well-structured with clear purpose sentence followed by bullet-list parameter details. Slightly verbose but each line adds value. Front-loading is effective.

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?

No output schema, but the description describes the content of each metric sufficiently for an agent to interpret return values. Could mention error handling or default behavior when date is null, but overall adequate.

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 coverage is 0% (no descriptions in the schema). The description fully compensates by explaining all enum values for 'metric' and specifying the date format. Adds complete meaning beyond schema titles.

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 'Get health metrics for a specific date' and lists all metric options with explicit return values. It distinguishes itself from sibling tools like garmin_activities and garmin_hr_trend by focusing on daily health metrics.

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 implies usage for retrieving health data by date and metric. It does not explicitly state when to avoid this tool (e.g., for weekly summaries) or mention alternatives, but the parameter options and sibling context provide indirect guidance.

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