Strava Quickstart

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds that it 'adapts to current state (env vars set? token present? what's next?)', which is useful behavioral context beyond the annotations. No contradictions.

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?

Two sentences, front-loaded with purpose and usage. Every word earns its place with no redundant content. Highly concise and well-structured.

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 simple tool with rich annotations and no output schema, the description covers purpose, usage, and adaptive behavior. It could explicitly differentiate from 'strava_onboarding' but still provides enough context for agent selection and invocation.

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 description does not mention the sole parameter 'response_format'. With schema description coverage at 0%, the description fails to compensate, leaving the agent to infer semantics solely from the enum and default. The parameter is simple, but the rubric requires the description to help when schema coverage is low.

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 this is a 'Personalized 3-step setup walkthrough' with a specific trigger: 'Call this first when the user asks "how do I connect Strava?"'. This distinguishes it from sibling tools like strava_get_auth_url and strava_onboarding by positioning it as the entry point.

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?

Explicit usage guidance is provided: 'Call this first when the user asks how do I connect Strava?'. This tells the agent exactly when to invoke this tool and indicates it is the initial step, effectively excluding alternatives.

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