garmin_hill_score

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and delivers almost nothing. It does not state whether this is a read-only computed metric, what data window is used by default, whether authentication/sync is required, or whether values are cached or computed on the fly. The only behavioral hint is the sub-score decomposition.

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?

It is a single short, front-loaded sentence with no filler, which is structurally clean. But given the complete absence of annotations and the undocumented days parameter, the brevity reads as under-specification rather than efficient conciseness.

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. Still, with no annotations at all, an undefined days parameter, and no routing guidance among ~50 sibling tools, the definition is not sufficient for an agent to invoke this correctly with confidence.

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?

There is a single 'days' parameter with a default of 30 and 0% schema description coverage, so neither the schema nor the description explains what the window means or how it affects the score. The description does not mention the parameter at all, leaving the semantics entirely undocumented.

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 names a specific Garmin metric ('hill score') and clarifies it decomposes into endurance and strength sub-scores, which adds a bit beyond the tool name. However, there is no verb and nothing distinguishes it from closely related siblings like garmin_endurance_score, garmin_vo2max, or garmin_race_predictions. The purpose is inferable but not sharp.

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?

No guidance on when to use this tool versus the many other score/summary siblings (garmin_endurance_score, garmin_training_status, garmin_fitness_age). There are no exclusions, no prerequisites, and no mention of the time window implied by the days parameter. The agent must guess from the name alone.

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