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's real added value is disclosing the payload contents — including sensitive health notes (medications, allergies, special needs, doctor) — which warns the agent it will receive PHI-like data. It does not mention pagination behavior, result ordering, or rate limits, so it adds only moderate context beyond the annotations.

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 sentences plus an endpoint reference, with the resource and returned data front-loaded and the filter surface second. Every clause maps to concrete information; only the trailing endpoint is arguably redundant.

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 compensates by enumerating the returned fields, which is exactly what an agent needs to judge whether this call answers its question. Combined with the fully documented input schema and read-only annotations, only pagination/ordering expectations remain unstated — a minor gap for an 11-parameter list tool.

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%, with all 11 parameters individually documented (page, page_size, date formats, is_active semantics), so the schema carries the burden. The description's filter list covers only 5 of the 11 parameters and omits page/page_size/created_date/updated_since/date_last_inactive, adding no format or interaction detail beyond the schema; 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 verb and resource ('List students') and then enumerates the returned fields and the filter surface, plus the backing endpoint GET /v1/Students. It is clearly a bulk-list tool, which distinguishes it implicitly from the singular jackrabbit_get_student, though it never names that sibling outright.

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?

'Filter by family, active status, location, last name or dates' signals the intended usage contexts, so an agent can infer this is the tool for filtered browsing of students. However, there is no explicit statement of when to prefer jackrabbit_get_student for a single record, or when to fall back to jackrabbit_list_families/contacts, leaving the routing to inference.

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