garmin_api_activity_workouts

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description usefully warns that raw JSON fields are not normalized, but its date-range sentence ('default to 7 days, at most 31 days') is orphaned — the schema exposes no date parameters — so it describes constraints the caller cannot exercise and sows confusion.

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?

Three short sentences with the subject front-loaded, so it reads quickly. However, the final sentence about date ranges occupies roughly a third of the text despite having no bearing on a tool whose only input is activity_id — it does not earn its place.

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-value documentation is not owed. For a one-parameter lookup, the essential omissions are only the meaning/source of activity_id and any note on how workouts relate to an activity; the stray date-range sentence is noise rather than a gap.

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?

There is a single parameter at 0% schema description coverage, and the description says nothing about activity_id — not its expected format, nor how to obtain a valid ID (e.g., from garmin_api_activities or garmin_api_activity_search). The date-range language does not map to any parameter in the schema.

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 phrase 'Workouts associated with an activity' names the resource and its binding to a single activity, which is enough to distinguish it from activity-level siblings like garmin_api_activity. There is no explicit verb ('retrieve/list'), but the noun phrase is unambiguous in context.

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 never states when to call this vs. garmin_api_activity, garmin_api_activity_search, or garmin_api_wellness_activities. The only comparative statement ('activity search uses pagination') describes a different tool's behavior rather than giving a selection rule for this one.

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