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

readOnlyHint=true already establishes that this is a safe read, so the description carries a lower burden, but it adds nothing beyond that: no mention of pagination, result ordering, whether deactivated classes are included, or the required organization scoping.

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?

A single short sentence with no waste, but it is a fragment that front-loads the resource at the cost of stating any action or scope. Compact without being informative.

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 list tool with no output schema, one undocumented required parameter, and no annotations beyond readOnlyHint, the definition should say what is returned and how it is scoped. Listing the entity's fields is a partial help but leaves the call semantics incomplete.

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% and the single required organizationId parameter is undocumented in both schema and description. The description never explains that results are scoped to one organization, which is the only parameter the agent must supply.

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 precisely – 'recurring class definitions' with the fields they carry – which implicitly contrasts with the sibling list_gym_class_sessions. However, it is a noun phrase with no verb, so the agent must infer from the tool name that it lists rather than fetches or mutates.

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 when-to-use statement, no prerequisites, and no explicit routing to alternatives such as list_gym_class_sessions or get_gym_class_roster. The distinction between class definitions and class sessions is left entirely for the agent to infer from the noun phrase.

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