Garmin Connect MCP

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 mentions the calculation is based on 'Jack Daniels training paces', hinting at a specific methodology, but does not disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence that front-loads the core purpose without any wasted words. It is appropriately sized for the tool's complexity and gets straight to the point.

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 has no annotations, no output schema, and 2 parameters with full schema coverage, the description is minimally adequate. It states what the tool does but lacks details on behavioral aspects like output format, error handling, or dependencies. For a calculation tool with no structured output information, more context would be helpful.

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 description coverage is 100%, with both parameters ('race_distance' and 'race_time') well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as explaining the relationship between the parameters or the calculation method. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the specific action ('calculate'), the resource ('Jack Daniels training paces'), and the input basis ('based on recent race performance'). It distinguishes itself from sibling tools like 'calculate_vdot_zones' or 'get_race_predictions' by focusing on training paces rather than zones or predictions.

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 implies usage when a user has recent race performance data to calculate training paces, but it does not explicitly state when to use this tool versus alternatives like 'calculate_vdot_zones' or 'get_training_plan_schedule'. No exclusions or prerequisites are mentioned, leaving some ambiguity.

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