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 'proper pagination support' and handling 'large datasets', which adds some behavioral context, but it lacks details on permissions, rate limits, error handling, or what the output looks like (e.g., format, pagination tokens). This is inadequate 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 directly states the tool's purpose and key feature (pagination for large datasets). It is front-loaded with no wasted words, making it easy to understand quickly.

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 no annotations, no output schema, and a tool that likely returns complex activity data, the description is incomplete. It doesn't explain the return format, error conditions, or behavioral nuances like how pagination works in practice (e.g., token-based vs. offset-based). This leaves significant gaps for an AI agent to use the 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 parameters (start, limit, activity_type) with descriptions and defaults. The description doesn't add any meaning beyond what the schema provides, such as explaining interactions between parameters or usage examples, meeting the baseline for high coverage.

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 as retrieving activities with pagination support, which is a specific verb ('Get') and resource ('activities'). It distinguishes itself from siblings like 'get_activities_for_date' by emphasizing pagination for large datasets, though it doesn't explicitly contrast with all similar tools.

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 for handling large datasets, suggesting when to use it (for paginated retrieval), but it doesn't provide explicit alternatives or exclusions. For example, it doesn't clarify when to choose this over 'get_activities_for_date' or other activity-related tools.

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