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

Annotations only declare readOnlyHint=true, so the description adds real value by disclosing the required OAuth scope (read:workout) and the underlying REST endpoint. It does not cover error behavior or rate limits, but the scope disclosure is meaningful beyond the annotation.

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?

Three compact segments (purpose, returned fields, REST/scope) with the purpose front-loaded. The field enumeration is list-heavy but earns its place since there is no output schema.

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 single-resource getter with no output schema, the description compensates by enumerating the returned fields, plus naming the endpoint and scope. Only usage routing and error/pagination behavior are absent, which is minor for a read-only one-param 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?

Schema coverage is 100% and the workoutId description already documents the UUID format and its source (whoop_list_workouts). The description adds only 'by its id', so the baseline 3 applies with the schema carrying the weight.

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 specific verb+resource ('Get a single workout by its id') and enumerates the returned fields (sport, strain, HR, distance, zone durations, start/end). The 'single' framing implicitly separates it from whoop_list_workouts, though it doesn't name that sibling explicitly.

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?

Usage is only implied: the workoutId schema description points to whoop_list_workouts as the source, which hints at the list-then-get workflow. There is no explicit when-to-use vs when-not guidance or any statement of the alternative to this tool.

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