Get WHOOP workouts

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

With no annotations, the description must carry the behavioral burden. It discloses that records are returned newest first, that distance/altitude are present only when GPS was recorded, and that the range is matched against the activity's own start/end window. It does not state read-only nature, auth requirements, or rate limits, but the field-level caveats are useful.

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?

Four sentences, each earning its place: return ordering, field semantics, parameter usage, and matching behavior. Front-loaded with the core resource fact and no filler.

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?

An output schema exists, so return value structure need not be described, but the description still explains key fields, pagination, and date-range matching. For a list tool with no annotations and full schema coverage, this is nearly complete, though read-only/auth context is absent.

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%, and the schema descriptions already explain start/end inclusivity/exclusivity and limits. The description reinforces that start/end select a range and next_token pages, adding the notable matching semantics, but does not add syntax or format beyond the schema. Baseline 3 is appropriate.

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?

States a clear resource: workout records, newest first. It describes fields (sport_name, score.strain, zone_durations, distance, altitude) which grounds the domain. It doesn't explicitly differentiate from sibling get_workout_by_id (single vs list), but the range-paging language implies a list.

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?

It says to use start/end to select a date range and next_token to page, which is procedural guidance for invocation. There is no when-to-use versus get_workout_by_id distinction, and no exclusions or alternatives named.

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