garmin_workout

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

No annotations are present, so the description carries full behavioral burden. It conveys that the tool returns a detailed read-only view rather than a list, and 'step-by-step' signals the granularity of the data. It does not disclose additional behavior such as authentication needs, error cases, or whether unsaved/planned workouts are accepted.

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 entire description is one short, front-loaded sentence with no filler. It states the key differentiating detail ('step-by-step') and the resource ('one saved workout') 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 single-parameter detail tool with an output schema present, the description is mostly sufficient. It falls slightly short of fully resolving how the agent obtains workout_id or distinguishes this from scheduled or activity-level detail, but the scope is clear enough for correct selection.

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 coverage is 100%, with workout_id described as 'Garmin workout id.' The description adds no further meaning beyond the schema, and the schema already sufficiently documents the single parameter. The baseline of 3 is appropriate because the schema carries the load.

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 identifies the resource as 'one saved workout' and specifies the output granularity as 'full step-by-step detail', making it distinct from the plural list tool garmin_workouts. It lacks an explicit verb such as 'retrieve' or 'get', but the resource and scope are clear.

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?

There is no explicit when-to-use guidance or mention of alternatives. The phrase 'one saved workout' implies this tool is for a single workout versus garmin_workouts, but the description does not tell the agent when to choose this over garmin_activity or garmin_scheduled_workouts. Usage is implied rather than stated.

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