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 the non-obvious semantic that records exist only where attendance was actually marked, which prevents an agent from reading an empty page as 'all present'. It stops short of describing pagination or ordering behavior, but page/page_size are documented in the schema.

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 short sentences, front-loaded with purpose, then return fields, then filters, then the endpoint. Nearly every clause carries information; only the trailing 'GET /v1/Attendance.' is close to filler for an agent that cannot issue raw HTTP calls.

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 usefully enumerates the returned fields and the available filters for a 10-parameter all-optional query tool, and annotations cover safety. Remaining gaps (sort order, whether has_scheduled_makeup and did_attend_makeup interact, empty-result meaning beyond the one parenthetical) are minor.

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 parameter baseline is 3. The description groups the filters into student, class, date range, attended and makeup status, matching most parameters, but omits page, page_size and updated_since, adding no detail beyond the schema.

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 attendance records') and then names the returned fields (student, class, date, attended, note, makeup). The parenthetical caveat that only marked-attendance dates appear meaningfully scopes it apart from roster/enrollment siblings, though it never names an alternative tool by name.

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 reader can infer when to use it (need attendance rows filtered by student/class/date/attendance status), and the 'only dates where someone marked attendance' note hints at when a result set will be empty. But there is no explicit when-not-to-use and no pointer to a sibling such as jackrabbit_get_class_roster for roster-style queries.

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