get_exercise_sets

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

With no annotations provided, the description carries the burden of behavioral disclosure. It highlights a key constraint (activity must be strength_training with sets), which is a notable behavioral trait. However, it does not disclose potential error behavior, what happens if the activity lacks sets, or explicitly confirm the operation is read-only beyond the verb 'Get'. This leaves some transparency gaps.

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 efficiently structured: a one-sentence summary of the tool's purpose, a usage note about applicable activities, and a single parameter description. It is front-loaded and contains no unnecessary filler or repetition.

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 one required parameter, no output schema, and no annotations, the description covers the essential aspects: what data is returned (per-set breakdown with fields) and when it is applicable (strength_training with sets). It does not explain edge-case behavior or error conditions, but for this level of complexity, the description is substantially 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?

The schema offers zero description coverage for the activity_id parameter, so the description's Args section is the primary source of meaning. It clarifies that the ID must correspond to a strength workout, adding context beyond the schema's mere 'Activity Id' title. This adequately compensates for the schema gap, though it could have included format or example guidance.

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 retrieves per-set strength data (exercise, reps, weight, est. 1RM) for a single activity, using the specific verb 'Get'. It distinguishes itself from sibling tools like get_activity (which likely returns a summary) and get_strength_history (which likely returns history) by focusing on the per-set breakdown.

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 provides a clear usage condition: 'Only meaningful for strength_training activities logged with sets on the watch.' This tells the agent when to use it (for strength workouts with sets) and implicitly excludes other activity types. However, it does not explicitly name alternative tools or provide a 'use this instead of X' statement, so it stops short of a 5.

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