get_strength_sets

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

With no annotations, the description carries the burden of disclosure. It explicitly states that rest periods are included and flagged, and that unclassified sets return a null exercise name. It also describes the output includes per-exercise rollup and total volume, adding valuable behavioral context beyond the schema.

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 focused paragraph that front-loads the core purpose, then details output components and edge cases. It is efficient without being terse, and the Args section provides clear parameter context. No filler, though some redundancy in describing the breakdown could be tightened.

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?

Given the tool's moderate complexity (one parameter, clear output structure) and the presence of an output schema, the description is reasonably complete. It covers input provenance, output content (working sets, rollup, volume, rest periods, nulls). It does not explicitly mention error cases or performance, but for a retrieval tool this is acceptable.

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 only parameter, activity_id, is described as 'The activity's numeric Garmin ID, from get_recent_activities.' This adds semantic meaning (numeric ID, source) that the schema (just a string type) lacks. With 0% schema description coverage, this compensation is essential and effective, though it could specify format (e.g., no URL encoding) but is 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 clearly states it provides a 'set-by-set breakdown of a logged strength session' with exercises, reps, and weight. This is a specific verb+resource and distinguishes from siblings like get_activity_details (which likely returns general activity info) and preview_strength_workout (which is for planned workouts).

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 explains it parses Garmin's recorded sets for a 'strength_training' activity and mentions the activity_id comes from get_recent_activities, giving context on how to obtain the required parameter. However, it does not explicitly state when not to use this tool versus alternatives, though the strength-specific focus implies it.

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