garmin_metric

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

With no annotations, the description carries the full disclosure burden. 'Fetch' indicates a read operation and the metric list scopes the behavior, but the description does not mention required authentication/session, rate limits, error behavior, or what happens when Garmin data is unavailable.

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 first sentence conveys the core purpose, followed by a compact parameter reference and three illustrative examples. There is no filler or repetition; every sentence contributes useful information.

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 tool has no annotations but does have an output schema, so return-value details are already covered. The description is complete for selecting parameters and forming calls, though it leaves minor gaps around Garmin session prerequisites and how this compares to sibling stat tools.

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?

Schema description coverage is 0%, yet the description fully compensates by documenting all four parameters: metric values, period choices/default, end_date format/default, and count meaning/default. The examples further clarify valid combinations.

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 opens with a specific action and resource: 'Fetch daily or weekly stat series from Garmin Connect,' and it enumerates the supported metrics. It clearly conveys what the tool does, but it does not explicitly differentiate it from sibling tools like garmin_stats or garmin_daily_summary.

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 clear invocation context: metric choices, period default, end_date format/default, and count default, reinforced by three concrete examples. It does not list exclusions or alternative sibling tools, but the usage context is explicit enough for correct selection in most cases.

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