Get Strava Training History

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

Annotations already signal readOnlyHint=true for safety. The description adds behavioral details: pagination with bounded pages, newest-first ordering, and timestamp constraints. No contradiction; context beyond 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?

Two efficient sentences: first states core purpose, second explains pagination and time range. Front-loaded, no extraneous words.

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?

Description covers pagination and time bounds but omits return format (e.g., full activity objects). No output schema. Still, it is complete enough for a read-only paginated tool with clear usage instructions.

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 coverage is 100% with descriptions for all 4 parameters. The description mentions 'nextPage' (not a parameter) and reinforces the use of after/before as Unix seconds, but adds little new semantic meaning beyond the schema.

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 verb 'Returns', resource 'activities', scope 'one bounded page', sorting 'newest first', and purpose 'long-term training analysis'. This distinguishes it from siblings like getRecentActivities or getActivities.

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 explains pagination logic ('When nextPage is non-null, call again') and temporal constraints ('Use after/before'). It positions the tool for 'long-term training analysis', but does not explicitly exclude alternatives or state when not to use it.

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