Garmin Connect MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't address other behavioral aspects like whether authentication is required, if there are rate limits, what the return format looks like (e.g., JSON structure), or if it's real-time vs. historical data. This leaves significant gaps for an agent to rely on.

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 ('Get daily respiration data') and includes key details ('breathing rate and patterns') without any redundant or unnecessary words. Every part of the sentence earns its place by specifying what data is retrieved.

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 lack of annotations and output schema, the description is incomplete for a data retrieval tool. It doesn't explain the return values (e.g., structure of breathing patterns), potential errors, or behavioral constraints like data availability or permissions. For a tool in a health/fitness context with many siblings, more context is needed to ensure reliable use.

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 input schema has 100% description coverage, with the single parameter 'date' well-documented in the schema itself (format, default). The description adds no additional parameter semantics beyond implying daily scope, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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 verb ('Get') and resource ('daily respiration data') with specific data types ('breathing rate and patterns'), making the purpose unambiguous. However, it doesn't explicitly differentiate this tool from potential sibling tools like 'get_hrv_data' or 'get_spo2_data' that might also relate to physiological metrics, which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives, such as other health data tools in the sibling list (e.g., 'get_hrv_data' for heart rate variability). It mentions 'daily' data but doesn't clarify if this is the only tool for respiration or if there are specific contexts (e.g., post-workout vs. sleep analysis) where it's preferred.

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