search-exercise-templates

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

The description adds caching behavior (fetches all on first call, caches in memory, refresh busts cache) beyond the readOnlyHint and openWorldHint annotations. No contradictions. Could mention potential staleness of cache.

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 effectively cover purpose and caching behavior. Every word earns its place; no fluff.

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?

The description covers purpose, caching, and parameter usage but does not mention the return format or pagination. With no output schema, the agent may lack information about what the response contains.

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 100% with descriptions, but the narrative adds context: 'case-insensitive substring' for query, 'bust the in-memory cache' for refresh, and 'optional filter to restrict results' for primaryMuscleGroup. This adds value beyond the schema.

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 verb 'search', resource 'exercise templates', and scope 'by name with optional muscle group filter'. It distinguishes from sibling tools like get-exercise-templates (which likely returns all without search) and get-exercise-template (single by ID).

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 mentions when to use the refresh parameter ('Use refresh:true to force a re-fetch') and explains caching behavior. However, it does not explicitly contrast with alternative tools like get-exercise-templates for retrieving all templates or get-exercise-template for a known ID.

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