getActivitySets

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

With no annotations, the description carries the full burden and does well: it discloses data provenance (.FIT file), ordering (order first done), field-level null behavior (weight absent when none was recorded), unit conventions (kg, seconds), and a staleness caveat. It omits what happens for non-strength activities (empty result vs. error) and any auth/rate-limit context.

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 what is returned, then field details, then the caveat. Every sentence adds information — the catalogue source, unit conventions, and the .FIT-vs-Garmin-Connect distinction all affect how an agent interprets results.

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?

No output schema and no annotations exist, so the description must convey the return shape, and it does so thoroughly: per-exercise entries, movement category, primary/secondary muscles, and per-set reps/weight/set time/restSec. The remaining gap is edge-case behavior for activities that are not strength training, which an agent would otherwise have to discover by trial.

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?

Only one parameter (activityId) and schema coverage is 100%, so the schema already fully documents it. The description only implies the activity scoping via 'of an activity' and adds no format, sourcing, or validity detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 resource and scope: strength training sets of an activity, read from the original .FIT file, one entry per exercise. This is clearly distinguishable from siblings like getActivityLaps (laps), getActivityWorkouts (workout definitions) and getActivity (summary), so an agent can route without opening a schema.

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?

It establishes the key selection condition: data comes from the .FIT file, and later Garmin Connect edits (renamed exercises, corrected reps/weights) are not included. That tells an agent when this source is and isn't appropriate. It stops short of naming an alternative tool for the edited view or stating prerequisites (e.g. activity must be a strength activity).

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