Garmin Daily Health Summary

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

Annotations already declare readOnlyHint and idempotentHint; the description reinforces 'Read-only and non-medical' and adds 'when available', which is behavioral context about data completeness not covered by 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?

Single sentence conveying purpose, data sources, and safety disclaimer. No wasted words; front-loaded with critical information.

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?

For a simple aggregator tool with an output schema, the description adequately covers purpose and behavioral caveats. Minor gap: no mention of return format or how missing data is handled, but output schema likely fills that.

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 67% (2 of 3 parameters documented). The tool description does not augment parameter meaning or add details for the undocumented 'response_format' parameter. Baseline 3 is appropriate given high coverage but lack of additional description.

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 builds a practical daily summary from multiple Garmin data sources (activity, sleep, HRV, etc.) when available, distinguishing it from individual metric-fetching siblings. The verb 'Build' and resource 'daily summary' are specific.

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 says 'practical daily summary' and 'Read-only and non-medical' but does not differentiate from the sibling 'garmin_get_daily_summary', leaving ambiguity about which to choose. No explicit when-to-use or when-not-to-use guidance is provided.

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