list_workouts

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without description help. The description adds useful scope context ('structured workouts saved in the account') and the limit's range, but says nothing about ordering, pagination beyond limit, or whether full workout detail is returned (an output schema exists, so the latter is forgivable).

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?

One sentence of purpose plus a compact arg note; nothing is wasted and the purpose is front-loaded. The args block is not redundant here because the schema has zero description coverage.

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?

For a one-parameter read tool with annotations and an output schema, the description is serviceable but thin. It omits result ordering and any indication of how many workouts typically exist or how to page past 100, which is the main thing an agent would need beyond the schema.

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 0%, so the description carries the burden for the single parameter, and it does: 'Maximum workouts to return (1-100). Defaults to 20' supplies both bounds and default that the bare integer schema lacks. It does not say what order results are returned in or whether limit is the only paging control.

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 ('List') and resource ('structured workouts saved in the Garmin account'), which is unambiguous against siblings like get_workout, create_workout, and schedule_workout. It does not explicitly name those siblings, but the list-vs-single-item distinction is inferable from the verb.

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?

Usage is implied: this is the enumeration call in a family that also has get_workout (single item) and get_activities (activities, not workouts). No sentence states when to use this instead of get_workout or what happens when there are no workouts, so the agent must infer routing from tool names alone.

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