list_garmin_workouts

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses ordering (most recent first), the returned fields, and a non-throwing auth failure mode. This gives the agent useful behavioral expectations that the annotations alone do not cover.

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 sentences with no filler: the first states the core behavior, the second explains the workflow purpose and sibling relationship, and the third covers the auth edge case. Information is front-loaded and every sentence earns 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?

For a read-only listing tool with one documented parameter, the description is complete: it names the output fields, ordering, and failure behavior. There is no output schema, so the explicit return-field list is valuable and sufficient for an agent to call it correctly.

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 single optional limit parameter is fully described in the schema with default, maximum, and semantics, so the 100% schema coverage earns the baseline. The description adds no additional detail about the parameter, but none is needed because the schema already carries that burden.

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 opens with a specific verb and resource: list workouts stored in the Garmin Connect account, and adds concrete details (most recent first, returning name/sport/workoutId). It references the sibling tools by name, making clear this is the list/index operation versus get/update/delete/schedule, so an agent can disambiguate immediately.

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 explicitly states the intended use: find a workoutId to pass to get_garmin_workout, update_garmin_workout, delete_garmin_workout, or schedule_garmin_workout. It also handles the auth precondition by saying that an invalid session produces a prompt to run authenticate_garmin rather than failing, which routes the agent to the correct alternative.

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