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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuine domain context beyond annotations – that both built-in and custom exercises are included and that kind determines applicable set fields – but says nothing about result size limits, ordering, or whether the full catalog is always returned.

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 tightly written sentences with no filler, and the return payload is front-loaded before the filtering caveat. The second sentence on kind and set fields is slightly tangential to listing but still earns its place.

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 one-optional-parameter read-only list tool with no output schema, the description covers what is returned, the filtering behavior, and the domain relevance of kind. Only pagination/limits and ordering are unaddressed, which is a minor gap at this complexity.

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 coverage is 0%, so the description must carry the single `query` parameter, and it does explain it as optional word-based filtering on the name. It leaves matching semantics ambiguous (substring vs whole word, whether multiple words are ANDed, case sensitivity), so it only partially compensates for the undocumented schema.

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 names the resource and the exact fields returned ("Exercise ids, names and kinds, built-in and custom"), so an agent knows precisely what it gets back. The verb is implicit (derived from name/title rather than stated), and no sibling is contrasted, which keeps it just short of a 5.

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?

Usage is only implied: the tool is for looking up exercises, optionally narrowing by name words, and the note that "the kind decides which set fields apply" hints it should be consulted before writing set data. There is no explicit when-to-use statement and no named alternative such as the add-exercise sibling.

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