Get Exam Dates

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

No annotations are supplied, so the description carries the full behavioral burden. 'Retrieve' signals a read-only operation and the enumerated content suggests a broad aggregate read, but there is nothing about authentication, whose data is returned (self vs. all students), or whether omitted parameters cause auto-discovery lookups. 'Capacities' and 'enrolled reservations' are left undefined, which matters for interpreting results.

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 front-loaded sentence with no filler; every listed item is a concrete data category. Slightly weakened by loosely defined list items ('capacities', 'enrolled reservations') that add breadth without precision.

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?

An output schema exists, so return formatting need not be explained, and both parameters are optional and fully documented. What is missing is the scoping and selection context an agent needs: how this differs from adjacent read tools and whether results are personal or term-wide. Adequate but with clear gaps for a tool sitting among many overlapping read siblings.

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 term_id's semester semantics and study_id's auto-discovery behavior are already documented in the schema. The description adds no meaning beyond that — it never mentions term scoping or the default-to-active-semester behavior. Baseline 3 applies when the schema does the heavy lifting.

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 ('Retrieve') and resource ('examination dates'), then enumerates the content areas: midterm test slots, enrolled reservations, capacities, deadlines. That is far more specific than the name alone. It stops short of a 5 because it never distinguishes this from siblings like get_registration_timeline or get_student_timetable, which plausibly overlap.

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 when-to-use guidance, no exclusions, and no named alternative. An agent cannot tell from this description whether exam dates belong here or in get_registration_timeline/get_student_timetable, nor that both parameters are optional and auto-resolved. Usage must be inferred entirely from the tool name.

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