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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing the shape of the returned payload (schedule, room, openings, waitlist counts, tuition, flags) and the underlying endpoint, but says nothing about pagination behavior or the default active-only scoping that the archived parameter implies.

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?

One front-loaded sentence that names the resource first and then the payload, followed by the endpoint. The field enumeration is long but each item is informative; nothing is wasted or repeated.

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, the description carries the burden of describing return values, and it does so thoroughly by listing the fields present on each class. Combined with a fully documented 8-parameter schema and clear read-only annotations, an agent has enough to call this correctly; only cross-tool routing guidance is missing.

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% and every parameter is documented inline, including defaults, ranges, and the next_page pagination hint. The description adds no parameter-level meaning beyond the field list, which is the expected baseline when the schema does all the work.

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 classes') and then enumerates exactly what each class record carries, so an agent knows this returns full class detail rather than just listings. It does not distinguish itself from siblings like jackrabbit_get_class (single class) or jackrabbit_list_class_listings, which is the only thing keeping it from a 5.

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?

There is no guidance on when to use this versus jackrabbit_get_class or jackrabbit_list_class_listings, nor any mention of common filter workflows (e.g., 'use student_id to get a student's schedule'). The schema's eight filters are never referenced in prose, so the agent must infer their purpose entirely from field descriptions.

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