garmin_list_workouts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add behavior beyond that. It adds the sort order ('newest first'), but discloses no details about pagination, maximum limit, or how the Garmin API's external state is reflected.

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, front-loaded with the action, with no filler. The resource and key ordering behavior are stated efficiently.

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 read-only, optional-parameter list call with an output schema present, the description covers the essential resource and ordering. The missing parameter elaboration and sibling routing reduce completeness, but low complexity and annotations prevent this from being a major 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?

The input schema has 0% description coverage for its single parameter, and the tool description does not mention limit at all. The parameter name and default value in the schema give some self-evident meaning, but the description adds no guidance on what limit is applied to or how it behaves.

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 uses a concrete verb ('List') and identifies a specific resource: workouts saved on the Garmin account. It also communicates ordering ('newest first'), though it does not explicitly contrast itself with similar sibling list tools such as garmin_scheduled_workouts.

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 is provided about when to use this tool over alternatives like garmin_scheduled_workouts, garmin_activities, or garmin_create_workout. The description states only what the tool does, leaving the agent to infer selection from the tool name and siblings.

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