get-exercise-history

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

The description implies a read-only operation ('Get past sets'), but with no annotations, it should disclose more about behavior, such as whether results are paginated, authorized, or return only sets for that specific template. The description provides minimal but non-contradictory information.

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?

Single sentence, 16 words, front-loaded with purpose. No redundant or extraneous information.

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?

Tool is simple with 3 parameters and no output schema. The description covers the essential: getting history with optional date filters. However, it could clarify that 'past sets' refers to sets performed in workouts using this template, or mention if history includes all-time data.

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 describes startDate and endDate with ISO 8601 format, but exerciseTemplateId lacks a description. The tool description adds context by stating 'for a specific exercise template', implicitly defining exerciseTemplateId. This compensates for the 67% 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 action ('Get'), resource ('past sets for a specific exercise template'), and optional filters. It distinguishes from siblings like get-exercise-template (which gets the template definition) and get-workout (which gets workout details).

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 alternatives. The description does not mention prerequisites, context, or exclusions. For example, it doesn't compare to get-exercise-template or get-workout history.

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