Get absences

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds value by detailing what the response includes (periods, excused status, notes, reminders, totals) and the default behavior of the `since` parameter, which goes beyond the schema. No contradictions.

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 description is a single sentence with no filler, but it packs several details into a moderate length. It is reasonably front-loaded, stating the main purpose before diving into nuances. Could be slightly more succinct, but overall efficient.

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 an output schema present, the description need not spell out every return field, so it is adequate for a read-only query with optional parameters. It covers the essential semantics and defaults, though it does not mention edge cases like empty results. Overall complete enough for correct invocation.

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 0%, so the description must compensate. It explains the `since` parameter's default (start of school year) and implies that `student` refers to the student whose absences are queried. However, it does not elaborate on the format or optionality of `student`, leaving some ambiguity.

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 clearly states that the tool retrieves absences for a student, and lists the key elements (periods, excused status, notes, reminders, totals). It is immediately distinguishable from siblings like get_grades or get_timetable because it is specifically about absences.

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 implies that this tool is used when you need absence records, but it offers no explicit guidance on when to use this tool versus alternatives such as get_briefing or other query tools. There is no mention of exclusions or preferred alternatives.

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