Strava MCP Server

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

With no annotations provided, the description carries the full burden and discloses key behavioral traits: it opens a browser window for secure authentication and enables activity tracking. It doesn't mention rate limits, error handling, or what happens post-authentication, but covers the core interaction well for a tool with no annotations.

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?

It is front-loaded with the core purpose, followed by behavioral details and usage guidelines in two efficient sentences with zero wasted words, making it easy to parse 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?

For a tool with no annotations, no output schema, and a simple input schema, the description is mostly complete—it explains what the tool does, how it behaves, and when to use it. It could improve by mentioning what data is accessed post-connection or error cases, but it's sufficient given the low complexity.

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 has 100% description coverage for its single parameter 'force', so the baseline is 3. The description adds value by implicitly contextualizing the parameter's use (re-authentication when already connected), though it doesn't explicitly mention the parameter. This elevates it above the baseline.

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 ('Connect your Strava account') and the purpose ('to enable activity tracking'), distinguishing it from sibling tools like check-strava-connection or disconnect-strava by focusing on initial authentication rather than status checking or disconnection.

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?

It provides explicit usage guidance with 'Use this when the user asks to connect, link, or authenticate their Strava account,' clearly indicating when to invoke this tool versus alternatives like check-strava-connection for verifying existing connections.

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