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. While it indicates this is a download operation, it doesn't specify whether this requires authentication, what permissions are needed, whether there are rate limits, what the output looks like (file content vs metadata), or any potential side effects. For a download tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 clearly states the tool's purpose. It's appropriately sized for a simple download operation and front-loads the essential information without unnecessary elaboration.

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?

For a download tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the download returns (raw file content, download link, metadata), whether authentication is required, what permissions are needed, or how to handle the downloaded data. Given the complexity of file operations and the lack of structured information elsewhere, the description should provide more contextual guidance.

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 clearly documented in the schema. The description mentions 'various file formats' which aligns with the format parameter, but adds no additional semantic context beyond what the schema already provides. This meets the baseline expectation when schema coverage is complete.

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 tool's purpose with a specific verb ('Download') and resource ('activity data'), and specifies the available file formats. However, it doesn't explicitly differentiate from sibling tools like 'get_activity_details' or 'get_activity_summary' which might provide similar data in different formats.

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. With many sibling tools that might provide activity-related data (like 'get_activity_details', 'get_activity_summary', 'get_advanced_running_metrics'), there's no indication of when this download tool is the appropriate choice versus those analysis/retrieval tools.

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