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

Annotations already establish a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds value by disclosing the returned payload contents (exercises, sets, reps, load, rest), which matters because no output schema exists. It omits behavior for a nonexistent workoutId, but is otherwise solid.

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?

A single front-loaded fragment that enumerates the returned fields with zero filler. It is telegraphic rather than prose, but every word earns its place.

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 single-entity read with full schema coverage and explicit safety annotations, the description covers what an agent needs: what is returned. Remaining gaps (not-found behavior, position relative to list_workouts) are minor for this complexity level.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents workoutId. The description adds nothing beyond implying the tool operates on a single identified workout; baseline 3 applies.

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?

"One workout with every exercise, sets, reps, load and rest" clearly identifies the resource (a single workout) and what it contains, distinguishing it implicitly from the plural list_workouts. It never names the sibling explicitly, but the singular framing plus detail enumeration makes the intent 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?

Usage is only implied by the singular "One workout" – an agent can infer this is the detail-fetch counterpart to list_workouts and requires an id. There is no explicit when-to-use/when-not, no mention of prerequisites, and no named alternative.

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