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

No annotations are supplied, so the description must carry the full behavioral load, and it does so credibly: it declares 'Read-only', spells out the return payload, says each result carries the next upcoming schedule, and explains the PWYC pricing model (priceCents = suggested, minPriceCents = floor, 0 = free). Gaps remain around pagination/truncation behavior and ordering, which matter for a search tool with a default limit of 10.

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 scope and filter facets come first, returns next, and the PWYC booking hand-off last — a sensible front-loaded order. It is slightly longer than needed; the returned-field enumeration could have been trimmed, but every sentence still serves a purpose.

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 available, the description usefully enumerates the response fields and mentions the embedded next-session schedule, which is exactly what an agent needs. For an eight-parameter, fully optional search tool the remaining shortfall is pagination and result-ordering semantics rather than core capability.

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 coverage is a middling 63%, and the description's facet list (query, city, discipline, date, session type, kind, format) maps loosely onto the eight parameters, adding some orientation. But the three undocumented parameters (city, type PRIVATE/GROUP, query) get no added meaning — notably it never says what fields 'query' matches against or how 'discipline' relates to the 'category' slug param.

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?

It opens with a specific verb and resource ('Search bookable classes, events, or retreats') and enumerates every filter facet, which is enough to tell it apart from search_mentors, search_studios, and search_videos without opening any schema. It also lists the returned fields, so the agent knows exactly what kind of entity comes back.

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 description makes clear this is the discovery step and even routes the agent forward: when pricingModel is PWYC, ask the user what they want to pay and pass it to book_class as pwycAmountCents. That cross-tool hand-off is genuine usage guidance. It does not, however, state when to prefer a sibling such as search_mentors or what to do if a search returns nothing.

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