Get activity laps

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

Annotations already declare it read-only, idempotent and non-destructive, so the description adds value by disclosing the network behavior: the FIT file is downloaded on first use and then cached. It also discloses what data comes only 'when the device recorded them', which sets correct expectations about missing fields — a detail annotations cannot convey.

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?

Front-loaded with the core purpose, then a dense field inventory, then usage and caching notes. The return-field sentence is long but each clause maps to real output content rather than filler.

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?

There is no output schema, so the description carries the full burden of describing return values — and it does so thoroughly, covering lap fields, swim-specific fields, multisport sessions, and FIT-only metrics, plus the caching behavior. An agent has enough to call it correctly and interpret the result.

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 description coverage is 100% and every parameter (activity_id, lap_offset, response_format) is documented in-schema, including the enum. The description adds no syntax or overflow guidance (e.g. when to use lap_offset on very long activities), so the baseline of 3 applies.

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?

States a specific verb and resource ('Get the laps... of one activity, from its original FIT file') and enumerates the returned granularity, so an agent knows this is the lap/session-level view rather than the activity overview. No sibling is named, so routing between it and garmin_get_activity or garmin_get_activity_streams is inferred rather than stated.

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?

'Use it for interval sessions, splits and pacing' gives concrete use conditions, and 'For a multisport leg ID, returns only that leg's laps' clarifies a scope boundary. It lacks explicit when-not guidance or a named alternative for activity-level summaries.

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