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

Annotations already declare readOnlyHint=true, so the description adds value by specifying that it returns the user's own catalog with specific metadata fields and that it holds the user's existing IDs. This is useful context beyond the annotation, though it doesn't mention pagination or auth requirements.

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 sentences, front-loaded with the primary purpose and immediately useful filter details. No filler or repetition; every sentence adds meaning.

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?

An output schema exists, so return format isn't needed. The description covers purpose, filters, and the distinction from search_exercise_pool, which is sufficient for a simple listing tool. The only gap is deeper parameter semantics, which is minor.

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?

The schema has zero parameter descriptions, so the description must compensate. It lists all four filters and explains that 'query' is a substring of name or id, but it doesn't describe allowed values or formats for muscle, equipment, or movement_pattern. This is partial compensation but leaves room for ambiguity.

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 tool lists the user's own exercise catalog with logged metadata and optional filters, and explicitly distinguishes it from search_exercise_pool for new exercises. This is a specific verb-resource pairing with clear sibling differentiation.

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 implies when to use it: to retrieve the user's existing exercises, and explicitly notes that new exercises come from search_exercise_pool. It doesn't explicitly say 'use this when you need the user's catalog' but the context makes it clear, and it names the alternative.

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