Strava Activities

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

Adds value beyond annotations by specifying required OAuth scopes (activity:read or activity:read_all). Annotations already indicate read-only and idempotent behavior, so the description complements with auth requirements. 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?

Three efficient sentences front-loaded with purpose, followed by filter/pagination capability and auth requirement. No fluff, every sentence earns its place.

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 the availability of output schema and rich annotations, the description covers the essential: purpose, filters, pagination, and auth needs. Complete for a list tool without missing critical context.

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?

Schema has 88% description coverage, so baseline 3. Description provides an overview of filters and pagination but does not add significant detail beyond what the schema already documents for each parameter.

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?

Clearly states the tool lists authenticated athlete activities, distinguishing it from sibling tools like strava_get_activity (single activity) or strava_get_activity_streams (streams). Specific verb 'list' plus resource 'activities' with scope context.

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?

Implies use when needing a filtered list of activities, but does not explicitly state when not to use or compare to alternatives. The mention of filters and pagination provides context, but lacks direct usage exclusions.

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