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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context by mapping to the underlying endpoint (GET /class/classschedules) and clarifying that results are templates rather than occurrences, but says nothing about pagination behavior, result volume, or default date-window semantics beyond what the schema carries.

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 tight clauses with the resource definition front-loaded and the endpoint reference appended as compact provenance. No filler sentences, nothing that fails to earn 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 read-only, zero-required-parameter list tool with full schema coverage and no output schema, this is close to sufficient: it identifies the resource, distinguishes it from occurrences, and hints at returned fields. It stops short of noting that results are paged/default-limited, which is the only meaningful gap.

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% across all 9 parameters, including defaults and range notes, so the schema carries the parameter burden. The description's field list (days, times, teacher, location) loosely corresponds to filterable dimensions but adds no syntax, id-format, or combining rules 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 as 'the templates that generate class occurrences', which is exactly the distinction an agent needs against sibling tools like mindbody_list_classes. It also enumerates what a schedule contains (days, times, teacher, location, date span).

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 explicit when-to-use/when-not statement and no sibling tool is named as an alternative. The template-vs-occurrence framing implies the right context (use this for recurring templates, not individual classes), but the agent must infer that routing.

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