search-exercise-templates

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It adequately covers the caching mechanism and refresh flag, but lacks details on error handling, rate limits, or return format. This is a moderate gap given the tool's complexity.

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 extremely concise, consisting of two sentences that efficiently convey the purpose, parameters, and behavioral nuance. Every sentence adds value without 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?

Considering the tool has no output schema, the description adequately explains input parameters and caching behavior. However, it omits details about the return structure (e.g., array of template objects with fields), which would enhance completeness for an agent selecting the tool.

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%, and the descriptions in the schema are already detailed. The tool description adds minimal value beyond paraphrasing those descriptions (e.g., 'optional muscle group filter'). The caching note does not directly enhance parameter understanding. Thus, a baseline score of 3 is appropriate.

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', the resource 'exercise templates', and the filtering mechanisms (name with optional muscle group). It effectively distinguishes this tool from the sibling 'get-exercise-templates' by focusing on search rather than listing all.

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 provides clear context by explaining the caching behavior and when to use the 'refresh' parameter. However, it does not explicitly state when to prefer this tool over alternatives like 'get-exercise-templates' for retrieving all templates without filtering.

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