get-activity-laps

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

No annotations are provided, so the description must carry the transparency burden. It discloses the data returned (per-lap metrics) but does not mention behavioral aspects such as whether the activity must have laps, error behavior, or any rate limits. The read-only nature is implicit in 'Returns' but not explicitly stated.

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, well-structured sentence that front-loads the action and lists the key metrics. Every word earns its place; there is no redundancy or 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?

With one simple parameter and no output schema, the description provides a reasonable summary of the return content (per-lap metrics with listed fields). It could mention units or the fact that laps are returned as an array, but the information is adequate for an agent to infer the tool's purpose and basic 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 input schema already fully describes the single parameter (activityId) with 100% coverage. The description adds little beyond reinforcing that it is for a specific activity, which is already in the schema. No additional meaning or constraints are provided.

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 returns per-lap metrics for a specific activity, enumerating the metric types (time, distance, speed, heart rate, cadence, power). The verb 'Returns' plus resource 'per-lap metrics' distinguishes it from sibling tools like get-activity-details and get-activity-streams.

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 provides clear context: use this tool when you need lap-level metrics for a specific activity, requiring an activityId. It does not explicitly name alternatives or state when not to use it, but the specificity of 'per-lap metrics' makes the use case obvious. No exclusions are mentioned.

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