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

Annotations only supply readOnlyHint=true, so the description carries the rest of the burden and does useful work by naming the exact result payload, which matters because there is no output schema. It stops short of disclosing pagination behavior (limit/offset defaults live only in the schema) or the client_id side effect noted there (client-specific pricing).

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 dense clauses: the scope/range constraint first, the returned payload second. Every element earns its place and the endpoint reference is a compact trailing tag.

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 14-filter read tool with no output schema and full schema coverage, the description is nearly complete: it conveys scope, result contents, and the upstream endpoint. The only material omission is any mention of pagination semantics, which is where an agent could stumble on large date ranges.

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 14 filters, so the schema already documents each parameter's semantics and defaults. The description adds only the generic notion of a 'date range', which is the baseline-3 case where structured data does the heavy lifting.

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 scheduled class occurrences') and enumerates the data returned — time, teacher, location, capacity, booked/waitlist counts, cancellation status — plus the underlying Mindbody endpoint. The word 'occurrences' implicitly separates it from mindbody_list_class_schedules (recurring templates), but that distinction is left for the agent to infer rather than stated.

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 date-range framing gives implied context for when the tool applies, but there is no explicit when-to-use vs mindbody_list_class_schedules or mindbody_get_class_visits, and no statement of prerequisites or exclusions. Usage must be inferred from the filters and the returned fields.

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