garmin_hydration

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

No annotations are provided, so the description carries the full burden. It adds meaningful behavioral context by explaining that the goal is calculated from activity, weather, and body weight and that under-hydration days are flagged, which helps interpret output. However it says nothing about auth requirements, data availability, or the meaning of the 'flags' output beyond the analysis itself.

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?

Front-loaded with the core statement ('Daily hydration intake vs goals'), followed by a compact explanation of the comparison logic. Every sentence earns its place; no filler or repetition.

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?

An output schema exists, so return values need not be described. For a read-only data query the description covers purpose and analysis adequately. The main gap is the undocumented time-range parameter, but overall it is complete enough to call the 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 parameter (days, default 30) has 0% schema description coverage, and the description does not mention it at all. It never clarifies what the time window means, acceptable range, or that the default is 30 days. The word 'Daily' hints at granularity but does not document the parameter.

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 resource (daily hydration intake) and the analysis performed (compares intake against Garmin's calculated goal, flags under-hydration days). An agent can distinguish it from generic siblings like garmin_goals or garmin_health_summary. It lacks an explicit sibling differentiation statement, but the resource is unambiguous.

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 never states when to use this tool versus alternatives such as garmin_goals or garmin_health_summary. Usage is only implied by the resource it describes. No prerequisites, no exclusions, no routing guidance.

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