get_activity_exercise_sets

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the source (Garmin Connect), and its one piece of behavioral context — "Dates are YYYY-MM-DD" — is irrelevant or misleading because the tool's sole parameter is activity_id, not a date.

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?

Very short and front-loaded, but it is under-specified rather than concise: the single parenthetical spends its words on an inapplicable date format instead of on the required identifier.

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?

An output schema exists, so return values need not be described, but the required activity_id is undocumented in both schema and description, and the description gives no sense of what an exercise set is. For a per-activity retrieval tool this leaves an agent unable to judge whether it satisfies the request.

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 0% and the description contributes nothing about activity_id — no format, no indication whether it is the numeric Garmin activity ID or a string, no note on the anyOf integer/string type. The only format hint given (date format) applies to a parameter that does not exist here.

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?

"Return activity exercise sets" names a resource, but "exercise sets" is Garmin-specific jargon that is not explained, and the description does not distinguish this from siblings like get_activity_details, get_activity_splits, or get_activity_typed_splits, which all sound like per-activity breakdowns.

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?

No guidance on when to use this versus the many other per-activity detail tools. There is no exclusion, no prerequisite, and no hint about what an "exercise set" contains relative to splits or details.

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