garmin_calories

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the conditional 'consumed (if logged)' availability and that data is drawn from two sources (daily_summary plus the calories table), which is genuine behavioral context. It says nothing about permissions, time-zone handling, or the aggregation window.

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?

Two short sentences, front-loaded with the metric breakdown and followed by a brief data-source note. No filler, though the second sentence is arguably optional given the output schema.

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?

The output schema covers return values, so the description needn't explain them. However, for a tool exposing only a 'days' window, the description never clarifies the time range or how the daily breakdown behaves across multiple days, leaving a real gap for a 1-param 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 single 'days' parameter (default 14) has 0% schema description coverage and is never mentioned in the description. The description says 'Daily' with no indication that a configurable multi-day window exists, so it fails to compensate for the schema gap.

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?

States a specific verb+resource ('Daily calorie breakdown') and enumerates the exact metrics returned (total, active, BMR, consumed). It clearly distinguishes itself from unlisted calorie-related siblings, though it doesn't explicitly differentiate from overlapping summaries like garmin_health_summary or garmin_today.

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?

There is no guidance on when to use this tool versus alternatives such as garmin_health_summary, garmin_today, or garmin_week_summary, which likely also surface calorie data. Usage can only be inferred from the metric list.

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