get-workouts

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

The description mentions pagination and ordering (newest to oldest), which are useful behavioral traits. However, with no annotations provided, it does not disclose read-only nature, rate limits, or other side effects, leaving a moderate gap.

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 brief and front-loaded with the most important information. Three sentences cover purpose, return details, and ordering without wasted words.

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 no output schema, the description adequately describes return fields (title, description, times, exercises). However, it lacks details on pagination metadata and how to handle large result sets, which is a minor gap.

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 0%, so the description must compensate. It mentions 'paginated' but does not explain page or pageSize parameters, their defaults, or min/max constraints. This adds little value beyond the schema.

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 'Get a paginated list of workouts', specifying the verb and resource. It distinguishes itself from sibling tools like get-workout (singular) and get-workout-count by emphasizing pagination and listing.

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 implies usage for listing workouts, but does not explicitly state when to use this tool versus alternatives like get-workout or get-workout-events. No guidance on exclusions or prerequisites.

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