Garmin Daily Health Summary

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

Annotations already declare readOnlyHint=true, so the agent knows it's safe. The description adds 'when available' indicating graceful handling of missing data, but does not disclose other behaviors like aggregation method or performance implications. The value beyond annotations is moderate.

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 concise sentence that delivers the core purpose and key constraints ('Read-only and non-medical,' 'when available') without 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 existence of an output schema, the description adequately summarizes the data sources included. However, for a composite summary tool, more context on what 'practical' means or how data is aggregated would be helpful but not critical.

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 input schema provides descriptions for 2 of 3 parameters (days, timezone) with reasonable clarity. The tool description does not add any further parameter context. Schema coverage is 67%, so baseline score of 3 is appropriate.

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 'Build a practical daily summary' from multiple Garmin data sources, indicating a composite aggregation. It distinguishes from individual metric getters but does not differentiate from the similarly named sibling 'garmin_get_daily_summary', leaving ambiguity.

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 like individual getters or the sibling 'garmin_get_daily_summary'. It only adds a disclaimer ('Read-only and non-medical') which does not help tool selection.

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