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

readOnlyHint=true already declares this as a safe read, so the safety profile is covered. The description adds the useful semantic that results are recurring templates rather than dated occurrences, but says nothing about pagination behavior or response shape.

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 compact sentences, front-loaded with the disambiguating definition followed by the endpoint. No filler.

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?

With no output schema, the description partially compensates by enumerating the fields returned (days, times, teacher, location, date span), and the readOnly annotation covers safety. Adequate for a 9-param optional-filter list tool, though pagination/return-size behavior is left to the schema.

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 all nine filters (limit, offset, dates, staff/program/location/session_type/class_schedule ids) are already documented. The description's mention of 'days, times, teacher, location and date span' loosely echoes the filterable dimensions but adds no syntax or default detail beyond the 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?

States a specific verb and resource ('List recurring class schedules') and immediately disambiguates the resource with 'the templates that generate class occurrences', which cleanly separates it from the sibling mindbody_list_classes (actual occurrences). The endpoint reference confirms scope.

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 template-vs-occurrence framing implies when to prefer this tool over mindbody_list_classes, but there is no explicit when-to-use statement, no exclusions, and no named alternative. Usage must be inferred from the parenthetical.

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