search_exercise_templates

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds that it's scoped to the account and searches by title, but doesn't describe pagination behavior or return semantics beyond what the annotations and output schema cover.

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 sentences with no waste. The search purpose is front-loaded followed by the call-order constraint.

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?

Output schema exists, so return values need not be explained. Combined with annotations covering safety, the description is nearly sufficient, though pagination details for page/page_size are absent. For a simple search tool this is largely complete.

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% for the three parameters (query, page, page_size). The description only implies title-based search, partially clarifying 'query' semantics but leaving page/page_size undocumented. Baseline 3 is appropriate given schema richness is minimal and description only aids one parameter.

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+resource (search exercise templates) with scope (account, by title). Distinguishes from siblings like create_routine/update_routine since it's a read-only search, but doesn't explicitly name the alternate tools for looking up templates.

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 provides when-to-use guidance: 'Call this before any routine/workout mutation.' This gives the trigger context. However, it doesn't name specific sibling alternatives (e.g., get_routine) or explain when-not to use it.

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