strava_activity_laps

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

The readOnlyHint annotation already signals this is a read-only operation, and the description aligns with that by saying 'fetch'. No extra behavioral details like return format or errors are provided, but the basic side-effect profile is transparent and consistent.

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, straightforward sentence with no unnecessary words or repetition. It is as concise as possible while remaining informative.

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?

The description provides enough context for an agent to understand the tool's basic function without ambiguity. It does not specify output details or typical use cases, but for a simple read-only fetch operation, the existing context is adequate.

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 single required parameter 'id' is described as 'Strava activity id', which fully clarifies its meaning. The schema description covers the parameter completely, and the tool description does not need to add further explanation.

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 fetches laps for one Strava activity, using a specific verb and resource. It distinguishes itself from sibling tools like activity_detail and activity_streams by focusing on laps specifically.

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 when to use it: when laps data for a single activity is needed. It does not explicitly name alternatives or conditions, but the purpose is clear enough that an agent would select this tool over others for lap-specific queries.

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