get-workouts

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

No annotations are provided, so the description carries the full burden. It discloses return fields, pagination, and ordering, but does not mention potential errors, rate limits, authentication requirements, or edge cases such as empty results.

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?

Two concise sentences deliver the core purpose, return fields, and ordering with no redundant information. The action is front-loaded.

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 list operation, the description covers the key aspects: pagination, return fields, and ordering. However, it lacks guidance on alternative usage scenarios and error conditions, though these are less critical given the tool's simplicity.

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. It mentions pagination and ordering, but does not explicitly explain the meaning of 'page' or 'pageSize' beyond their names; the schema provides defaults and constraints, but the description adds little detail about how these parameters affect results.

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 the specific verb 'Get' and targets 'a paginated list of workouts,' clearly distinguishing it from singular get-workout and get-workout-count siblings. It also lists the returned fields and ordering, making it unambiguous.

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?

Provides clear context as a paginated list operation, implying it is for bulk retrieval versus single-item alternatives. However, it does not explicitly state when not to use it or name alternative tools, lacking explicit exclusions.

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