get-exercise-history

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

Annotations already declare readOnlyHint=true, describing it as a read operation. The description adds the concepts of 'past sets' and date filtering, which are consistent. However, it does not disclose other behavioral traits like pagination, ordering, or limits, which would be helpful.

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, concise and front-loaded with the core action. Could be slightly expanded to include response format without losing efficiency.

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?

Without an output schema, the description does not specify what 'past sets' includes (e.g., reps, weight, date). Given 3 parameters and no output schema, some additional context about the response structure would improve completeness.

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?

Input schema covers 67% of parameters with descriptions (startDate and endDate have ISO 8601 format notes). The overall tool description mentions optional date filtering, aligning with schema. However, the required exerciseTemplateId parameter lacks description in both schema and tool description, leaving ambiguity.

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?

Description clearly states 'Get past sets for a specific exercise template', specifying the verb, resource, and optional filtering. This distinguishes it from sibling tools like get-exercise-template or get-workout, which serve different purposes.

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 explicit guidance on when to use this tool versus alternatives like get-workout or get-exercise-templates. The description implies usage context (getting history for a specific exercise template), but does not state when not to use it or provide alternatives.

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