get_workout

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

The description adds pagination behavior ('Split output is paginated') and mentions data availability, which are not captured by the annotations (readOnly, idempotent, etc.). It does not contradict any 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?

Two concise sentences with the main purpose front-loaded. No filler or redundancy; every word adds value.

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 read-only tool with no output schema, the description gives a reasonable overview but omits details on response structure and how pagination parameters control output. It is adequate but leaves gaps for an agent to fully understand invocation.

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 only 33% (only workout_name is documented). The description mentions pagination but does not explain split_limit or split_offset, leaving these parameters unclear. It fails to compensate for the low schema coverage.

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 clearly states the tool's action ('Read one workout summary') and specifies the returned elements: recorded activity type, available splits, and data availability. It distinguishes itself from list_workouts (which lists) by focusing on a single workout, and from get_workout_series by its singular nature.

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?

No guidance on when to use this tool versus its siblings. It does not mention list_workouts or get_workout_series, nor does it provide conditions or exclusions. The agent must infer usage from the name and context.

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