prs

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

With no annotations, the description carries the burden of behavioral disclosure. It specifies what data is returned (heaviest weight, best estimated 1RM, most reps), but does not explicitly state that the operation is read-only or has no side effects. It also leaves 'all-time' and the exact computation of estimated 1RM open to interpretation. The description adds context beyond the name but could be richer.

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 single sentence that front-loads the record types and clearly states the scope. Every word earns its place; there is no filler or redundant 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?

For a single-parameter tool with no output schema and no annotations, the description provides the essential information: what records are returned and how to scope them to one exercise or all. It does not detail the return format, but that can be inferred from the record types listed. It also lacks a note distinguishing it from sibling tools, but it is still sufficient for invoking correctly.

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 provides only a nullable string parameter with no description, so coverage is 0%. The description compensates by explaining how the parameter behaves: providing an exercise returns records for that exercise, while omitting it returns records for all exercises. This fully addresses the intended use of the only parameter.

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 identifies the tool as returning all-time personal records, listing concrete record types (heaviest weight, best estimated 1RM, most reps) and specifying the scope (one exercise or all). Although the verb is implied rather than explicit ('get' or 'list'), the resource is unambiguous and distinct from sibling tools like exercise_history or weekly_volume.

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?

There is no guidance about when to choose this tool over alternatives such as exercise_history or weekly_volume. The only usage hint is the optional exercise filter, which is more about parameter semantics than decision-making; no conditions or exclusions are provided.

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