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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds a modest operational signal ("Mindbody calls: 1") that hints at API cost, but says nothing about pagination behavior, the includeInactive default of true, or what the filtered/unfiltered result sets look like.

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 text is short, but the opening line is boilerplate that duplicates the title and exposes a raw endpoint path, and the capitalized parameter names don't match the schema's camelCase. The one substantive sentence does arrive quickly, so it isn't padded, just partly wasted.

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 read-only, ten-parameter listing tool with full schema coverage and clear annotations, the essentials are present and the scheduled-class filter note is genuinely useful. However, it never explains the resource itself or how it relates to the many sibling class/reporting tools, leaving an agent to guess at the boundary.

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 100%, so the schema already documents all ten parameters well, including date formats and the includeInactive default — that establishes a baseline of 3. The description only re-lists four filter parameters (with inconsistent capitalization: StaffId vs. staffId) and adds no meaning beyond what the schema states more precisely.

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 states a verb and resource ("Get Class Descriptions") plus the underlying HTTP path, but the first clause is essentially a restatement of the tool name and title, adding no explanation of what a "class description" actually is. The second sentence pivots to filtering behavior rather than clarifying purpose, and there is no differentiation from siblings like find_classes, get_class_visits, or get_session_types.

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?

It gives one concrete usage condition: pass staffId, startClassDateTime, endClassDateTime, or locationId to get descriptions tied to scheduled classes. That is a real when-to-use hint, but it only covers one scenario — there is no guidance on when to call this instead of find_classes or get_session_types, and no mention of the unfiltered case returning all descriptions.

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