hevy_search_exercise_templates

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

With no annotations, the description fully discloses behavioral traits: case-insensitive substring matching, pagination limited to 30 pages of 100, truncation flag, total_matches as lower bound when truncated, and a one-hour catalog cache. This goes beyond basic disclosures.

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 two concise sentences plus a brief response format explanation. Every sentence adds value—no fluff, front-loaded with core purpose, and efficiently covers behavior and usage context.

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?

Given the moderate complexity (search with pagination and truncation) and the absence of an output schema, the description thoroughly explains response fields (query, total_matches, exercise_templates, truncated) and the truncation behavior. It fully equips the agent to understand outcomes and limitations.

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?

Both parameters have schema descriptions, but the description adds significant value: it clarifies query is 'case-insensitive substring matched against the template title' and provides default value for limit (25) and explains that total_matches reports the full count even if truncated.

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 'Find exercise templates by name' and specifies it paginates the full catalog, returning case-insensitive substring matches. It distinguishes from siblings by explicitly saying to use it to resolve an exercise_template_id from a human name before composing a workout or routine, differentiating it from listing all templates or getting 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 explicitly explains when to use this tool: 'Use this to resolve an exercise_template_id from a human name... before composing a workout or routine.' It implies not to use it if you already have the ID, but does not provide explicit exclusions or alternatives.

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