Get exercise templates

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

No annotations exist, so the description must disclose behavior. It mentions pagination and that both built-in and custom templates are included. However, it does not describe ordering, filtering, or response format, leaving some behavioral aspects unclear.

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?

Single sentence, front-loaded with the verb 'Get', includes key qualifiers (paginated, built-in/custom). No wasted words, easy to parse.

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?

For a simple list tool with two params and no output schema, the description covers the main purpose and scope. It could mention that pagination is controlled by page/pageSize parameters, but those are in the schema. Minor gap: no mention of sorting or filtering.

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 covers both parameters (page and pageSize) with descriptions. The tool description does not add new semantic information about the parameters beyond what the schema provides. Baseline 3 applies due to 100% schema coverage.

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?

Verb 'Get' and resource 'paginated list of exercise templates' clearly states what the tool does. It distinguishes from sibling 'get-exercise-template' by specifying 'list' and including 'built-in and custom'. The scope 'available on the account' adds context.

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?

No explicit guidance on when to use this tool versus alternatives like 'get-exercise-template' or when not to use it. The description only states what it does, not the context of its use.

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