garmin_get_day

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

Annotations already declare readOnly, idempotent, and openWorld hints, so the safety profile is covered. The description adds that the summary is 'consolidated' but does not disclose behavior like the refresh parameter effect, caching, or whether it aggregates from multiple Garmin endpoints. It adds some context but not rich detail.

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, front-loaded sentence with no filler. Every word contributes to conveying the tool's core purpose and date format.

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 and the presence of an output schema (which documents return values), this is borderline adequate. However, the unexplained 'refresh' parameter and lack of guidance on when to use this tool vs. more specific ones leave meaningful gaps. It is minimal but incomplete.

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, and the description only hints at the 'day' parameter via 'YYYY-MM-DD date'. The 'refresh' boolean parameter is completely undocumented in both schema and description, leaving significant ambiguity. The description does not compensate for the missing parameter semantics.

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 precisely identifies the tool as retrieving a 'consolidated health summary' for a specific single date ('YYYY-MM-DD'). This clearly distinguishes it from sibling tools like garmin_get_sleep or garmin_get_activity, which focus on individual data types.

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 conveys clear usage context: this is for a one-day consolidated overview. It does not explicitly name alternatives or exclusions, but the scope ('one date' + 'consolidated') implies when it's appropriate. This meets the 'clear context, no exclusions' level.

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