list_workouts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description adds only that these are the user's saved workouts. It says nothing about ordering, pagination behavior, truncation at the limit, or empty-library behavior for a listing endpoint whose results can be capped.

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?

It is a single short fragment with zero waste, but it is under-specified rather than deliberately concise – there is no leading verb and no second sentence to carry usage or pagination guidance.

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?

The output schema covers return values and annotations cover the read-only profile, so the description need not explain those. However, for a paginated list tool with a capped limit it should at least mention that results are capped and how to see more.

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% for the single 'limit' parameter, and the description never mentions it. The schema shows a default of 30 and a maximum of 100, but nothing explains what the limit counts or what happens when the library exceeds it, so the description fails to compensate for the coverage gap.

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 'Saved workouts in the user's Garmin library' identifies the resource and implicitly the retrieval act, and the word 'Saved' hints at a distinction from get_scheduled_workouts. But there is no verb (list/fetch) and no explicit statement of what is returned or how it differs from list_activities or get_scheduled_workouts, leaving purpose merely inferable.

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?

Nothing states when to call this versus get_scheduled_workouts, list_activities, or get_activity, despite those siblings being obvious alternatives in the same library. No prerequisites or context of use are given.

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