garmin_workouts

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

With no annotations, the description must disclose behavioral traits. It only states that the tool lists templates with summarized fields, but does not clarify pagination (despite limit/start parameters), read-only nature, or any side effects. The word 'List' implies reading, but not explicit.

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?

The description is a single concise sentence of 8 words, but this brevity sacrifices essential details like parameter usage and behavioral context. It is appropriately short for the tool's simplicity, but could be restructured to add value.

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?

Given the simple tool with 2 parameters and no annotations, the description omits pagination, parameter explanations, and differentiation from siblings like garmin_scheduled_workouts. The presence of an output schema (unseen) may compensate slightly, but the description remains incomplete.

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 must compensate by explaining the limit and start parameters. It fails to mention them at all, leaving the agent without guidance on how to use pagination.

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 specific verb ('List') and resource ('saved Garmin workout templates') with an additional qualifier ('summarized fields'), clearly distinguishing it from sibling tools like garmin_activity (single activity) and garmin_scheduled_workouts (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?

The description provides no guidance on when to use this tool vs. alternatives, such as garmin_scheduled_workouts or garmin_recent_activities. The single sentence lacks context for when to choose it over siblings.

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