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

Annotations already declare this as a read-only, idempotent, non-destructive operation, so the burden is lighter. The description still adds genuinely useful behavior beyond them: the 31-day maximum window, sorted output, paging handled internally, and an explicit cost model of one Mindbody call per 200 classes capped at five. It does not explain failure modes or whether results can be truncated at the call cap.

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?

Three tightly packed sentences that lead with what is returned, then filtering, then limits and cost, then when to use it. The middle sentence enumerating filters is somewhat redundant with the schema, but nothing is padded or buried. Front-loading is good.

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 12 optional parameters, no output schema, and no required arguments, the description carries the return-shape burden and does so by listing the row fields. It also discloses the date-window cap, cost ceiling, and sorting behavior. The only gap is that it does not say what happens when the five-call cap is hit or whether results are truncated.

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 every parameter including defaults, enums, and lookup hints (get_programs, get_class_descriptions). The description mostly restates the filter set and the 31-day bound rather than adding new semantics. Baseline 3 applies.

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 opens with a specific resource and scope: classes within a date range returned as compact rows, and it names the actual row fields (time, name, staff, location, capacity, spots left). It is clearly a schedule-browsing/search tool rather than an attendance or revenue report. It stops short of naming which sibling tool to pick instead, so it is clear but not fully differentiated.

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 closing sentence gives a concrete usage context: browsing the schedule or looking for open spots. That is enough to steer an agent away from attendance/summary siblings. There is no explicit when-not guidance or named alternative tool, so it misses the top band.

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