garmin_list_workouts

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. Description adds no additional behavioral traits beyond listing workouts, so it does not significantly improve transparency beyond what annotations already provide.

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?

Very concise: one sentence for purpose, one sentence for usage context, then clear Args and Returns sections. No wasted words, front-loaded with key information.

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?

Covers purpose, usage context, parameters, and return format adequately. Lacks details on ordering or error messages beyond a generic 'Error: ...', but annotations and output schema (present per context) likely fill gaps. Minor omission of pagination behavior, but limit parameter implies a capped list.

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?

Despite schema description coverage being 0% (per context), the description explicitly lists parameters with their valid ranges (limit 1-100) and options (response_format markdown or json), fully compensating for the lack of schema descriptions.

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?

Describes clearly that the tool lists saved workouts with their IDs, and mentions its utility for obtaining workout_id for scheduling or deletion. Distinguishes from sibling tools by specifying the resource (saved workouts) and linking to specific dependent tools.

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?

Explicitly states when to use this tool (to get workout_id for schedule or delete), providing clear usage context. Does not mention when not to use or alternatives, but context is sufficient.

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