hevy_get_exercise_history

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

With no annotations, description carries full burden. It discloses that results include warmups/dropsets/failures, pagination details, date-range filtering, and default ordering (newest-first, all time). Does not mention rate limits or pagination error handling, but sufficiently covers behavior for a read operation.

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?

Three sentences, each earning its place: first states purpose, second explains filter modes, third describes default behavior. No wasted words, information front-loaded.

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 5 parameters and no output schema, description covers purpose, filtering, ordering, and row content. Lacks details on return format (e.g., pagination metadata) but is still fairly complete for a list tool. Minor gap in error behavior.

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 descriptions cover 80% of parameters. Description adds value by explaining that filters are combinable, that without start_date/end_date results span all time, and defaults for page/pageSize. Could clarify that exerciseTemplateId is required, but overall adds meaningful context.

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 it lists logged sets for a specific exercise template, specifying verb (List), resource (exercise history), and what is included (warmups/dropsets/failures). This distinguishes it from sibling tools like hevy_list_workouts (workout-level) and hevy_get_workout (single workout).

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?

Description explains when to use: to get history for a given exercise template. Mentions two filter modes and default time span. Does not explicitly list when not to use or alternatives, but the purpose is clear enough to guide selection.

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