list_workouts

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

There are no annotations, so the description carries the full burden. It does disclose the sort order ('most recent first') and scopes the operation to saved templates, and the verb 'List' implies a read-only operation. However, it does not explicitly state read-only behavior, side-effect-freeness, or any authentication or data-freshness considerations.

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 compact and front-loaded with the core purpose, followed by a clear Args section. Every sentence carries useful information, with no filler or repetition.

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 simple two-parameter list operation with no output schema, the description covers purpose, scope, ordering, and pagination semantics. It leaves some room for more context about the shape of returned workout objects, but nothing critical is missing for selecting and invoking the tool 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?

Schema description coverage is 0%, but the description fully compensates by explaining both parameters: 'limit: Maximum number of workouts to return' and 'start: Number of most-recent workouts to skip (for pagination).' This adds meaningful semantics beyond the schema's bare types and defaults.

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 clearly states the verb and resource: 'List the athlete's saved workouts (templates), most recent first.' The parenthetical '(templates)' distinguishes this from list_activities and get_scheduled_workouts, while the ordering note adds concrete detail.

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 phrase 'saved workouts (templates)' implies this tool is for listing saved template workouts rather than activities or scheduled workouts, but the description does not explicitly state when to choose this tool over siblings like list_activities, get_workout, or get_scheduled_workouts. Some inference is required, so it earns the implied-usage score rather than a higher one.

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