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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the returned fields and the underlying GET /v1/ClassListings endpoint, but says nothing about pagination, auth requirements, or how include_closed interacts with organization settings beyond what the schema states.

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?

A single dense sentence front-loads the resource and its contents, then the filters, then the endpoint. No wasted clauses, though the long comma-separated run makes it slightly harder to scan than a split sentence would.

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 13 optional params, no output schema and no nested objects, the description compensates well by listing the fields the listing returns (openings, age ranges, tuition, address, registration links). The missing piece is routing versus jackrabbit_list_classes and any pagination note, but overall it is sufficient to call correctly.

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 all 13 parameters including pagination and include_closed. The description's filter list roughly mirrors the schema parameters (category, instructor, days, session, location, gender, room, status) without adding format, id-lookup, or combination semantics, so the 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?

States a specific resource (public-facing class schedule/class listings) and enumerates the fields returned plus the filterable dimensions, so an agent knows what it gets. It does not, however, distinguish itself from the sibling jackrabbit_list_classes, which an agent could easily confuse it with.

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 phrase 'public-facing ... with openings' hints at the scenario, but there is no explicit when-to-use, when-not-to-use, or pointer to jackrabbit_list_classes as the alternative for internal/all-class data. Usage must be inferred entirely.

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