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 adds useful context about response size optimization for Claude's context window and warnings about large data with 'include_raw', which helps the agent understand performance implications. However, it doesn't cover other behavioral aspects like authentication requirements, rate limits, or error conditions.

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 appropriately concise with two sentences that each serve distinct purposes: the first states what the tool does, the second provides important behavioral context about response optimization. There's no wasted verbiage, though it could be slightly more structured with clearer separation of concerns.

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 read operation with 4 parameters and no output schema, the description provides adequate but incomplete context. It covers the core purpose and response size considerations, but doesn't explain the relationship to sibling tools, return format, or error handling. With no annotations and no output schema, more guidance would be helpful for an agent to use this tool effectively.

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%, so the schema already documents all four parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it mentions response size optimization generally but doesn't explain how individual parameters contribute to this. 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 tool's purpose with a specific verb ('Get') and resource ('comprehensive activity metrics'), including the types of data returned (splits, advanced metrics, performance data). However, it doesn't explicitly differentiate this tool from sibling tools like 'get_activity_summary' or 'get_advanced_running_metrics', which appear to provide overlapping functionality.

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 available (e.g., 'get_activity_summary', 'get_advanced_running_metrics'), there's no indication of what makes this tool distinct or when it should be preferred over others for activity data retrieval.

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