search_exercise_templates

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

With no annotations, the description carries the burden and does well by disclosing the cached local execution and sorted output ('Runs locally against a cached copy' and 'Returns top matches sorted by score'). It could mention staleness of the cache, but the disclosed traits are valuable.

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 sentences, front-loaded with purpose, and every sentence adds value (e.g., performance advantage, ordering). No fluff or redundancy.

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?

Despite no output schema or annotations, the description fully covers what this tool does, when to use it, and what it returns. It sufficiently differentiates from sibling search/list/get tools and provides a complete picture for selection.

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 0%, so the description must compensate. It explains 'query' (fuzzy search by name) and 'muscleGroup' (optional filter), but only implies the meaning of 'limit' via 'top matches.' The limit parameter's semantics remain incomplete.

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 states the tool's function: 'Fuzzy-search exercise templates by name with an optional muscle-group filter.' This is a specific verb+resource+options, distinguishing it from siblings like list_exercise_templates and get_exercise_template.

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?

Explicitly differentiates from the alternative of paginating /v1/exercise_templates by stating it 'runs locally against a cached copy of all templates — much faster and cheaper.' This gives a clear when-to-use recommendation.

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