whoop_get_workout

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

With no annotations, the description carries the disclosure burden but only lists output fields. It fails to disclose that heart rate zones are only included when the include_zones parameter is set to true (as per the schema default false), and gives no information about error behavior, authentication, or caching.

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 a single concise phrase, using only 11 words to convey the tool's purpose and output. It is well-structured as a front-loaded summary, though it is a fragment rather than a full sentence, which slightly reduces clarity.

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 retrieval tool with no output schema, the description lists the main fields returned, which is helpful. However, it omits the conditional behavior of heart rate zones, the effect of response_format, and any error/edge-case behavior, leaving gaps for an agent deciding how to invoke and interpret the tool.

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?

The input schema provides complete descriptions for both parameters (include_zones and response_format), achieving 100% schema coverage. The description adds no parameter-specific semantics, but the baseline of 3 applies because the schema itself is self-sufficient.

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 explicitly identifies the tool as returning the 'Latest workout' and enumerates the included attributes (sport, duration, strain, distance, heart rate zones, altitude). It distinguishes itself from the sibling tool whoop_get_workout_history by focusing on the single most recent workout.

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 retrieving the most recent workout but provides no explicit when-to-use guidance or comparison against alternatives. There is no mention of when to prefer this over whoop_get_workout_history or other get_* tools.

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