get_exercise_detail

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

With no annotations, the description carries the transparency burden. It discloses caching behavior ('Reuses the cached workout-details response'), the need for team resolution via program_id/team_id, and the scope (per-set data for one exercise). It doesn't explicitly state read-only or error behavior, but the 'get' semantics and level of detail are sufficient for typical use.

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 three sentences, front-loaded with the main purpose, and free of fluff. Every sentence adds value: purpose, usage context, and parameter guidance.

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 tool with 4 parameters and no output schema, the description covers purpose, usage context, and most parameters. It lacks an explicit mention of program_workout_id and return-value shape, but the caching note and 'per-set data' hint give enough context for an agent to proceed. Slightly more detail would make it complete.

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 0%, so the description must explain parameters. It explains exercise_id and team_id/program_id ('Pass the exercise_id shown... plus the same program_id/team_id you used there'). However, it omits program_workout_id, a required parameter, leaving a gap for that key identifier.

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 opens with a specific action and resource: 'Get the full, un-slimmed per-set data for ONE exercise within a workout.' It explicitly distinguishes itself from the sibling get_workout_details by noting this returns per-set data without pulling the entire session, making its scope clear.

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 provides clear guidance: 'Use this after a slim get_workout_details call' and explains the trade-off (get every logged set without pulling the entire session). It also specifies the prerequisite of reusing the cached workout-details response and what parameters to pass, giving actionable when-to-use context.

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