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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the shape of the result (per-session sets, volume, estimated 1RM, heaviest set, trends) and the timezone semantics distinguishing local_date from the UTC date.

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 focused sentences, front-loaded with the purpose, then return content, then the one non-obvious semantic (date vs local_date). No filler, though the timezone sentence is dense and slightly tangential to selecting the tool.

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?

With a 2-parameter schema at full coverage, a read-only annotation profile, and an output schema, the description covers all that is needed to call and interpret the tool. The only gap is deciding when this tool is preferred over sibling lookups, which is a minor omission.

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 description coverage is 100% – both exercise_name (exact, case-insensitive, no partial matching) and limit (default 10, max 50) are fully documented in the schema. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Get performance history for a specific exercise across sessions') and immediately enumerates the returned metrics, which clearly differentiates it from search_exercises and validate_exercise_names. An agent can identify this as the historical-performance lookup without opening the schema.

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?

Usage is implied: fetch history for a named exercise that the agent already knows. There is no explicit when-to-use/when-not, no mention of prerequisites such as validating the exercise name first (validate_exercise_names exists as a sibling), and no routing to alternatives.

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