find_exercises

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds useful non-annotation detail: results are ordered most-recently-done first, and the default result set is limited to exercises the user has performed, including frequency and recency of last performance.

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?

Two short lines with no filler, and the core search semantics are front-loaded before the default-behavior caveat. Slightly hurt by the trailing line break and the informal bullet-like second sentence, but size is appropriate.

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?

An output schema exists, so return values need not be explained, and the description correctly notes the caller gets frequency and last-performed data. However, it omits what an empty query plus only_used=false returns and any result-count or pagination limits — meaningful gaps for a search tool with three undocumented parameters.

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 coverage is 0%, so the description has to carry parameter meaning. It does map loosely onto all three ('by name' for query, 'muscle or group' for muscle, 'by default only exercises the user has done' for only_used), but it never states that only_used=false returns the full exercise catalog, nor how name and muscle filters combine, nor expected value formats for muscle.

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: search exercises by name and/or muscle group, with examples of muscle values. That clearly separates it from most siblings, though it does not explicitly distinguish itself from get_exercise_history, another exercise-oriented tool in the list.

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?

The description conveys the default context ('by default only exercises the user has done') but never says when to prefer this over get_exercise_history or what changes if only_used is turned off. Usage is implied by the query semantics rather than stated.

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