Export Exam Schedule (.ics)

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

Goes well beyond annotations: documents the exact output field ('ics'), edge-case behaviors ('skipped', 'not_found', 'exam_schedule_not_published', 'end_time_unknown'), time zone, and crucially that it does not write a file. Annotations confirm read-only, but the description adds rich behavioral detail about error states and output semantics.

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?

Front-loaded with the main action and output, then lists edge cases efficiently. Two long sentences but no filler; every clause carries information about behavior or output.

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?

Covers output location ('ics'), non-file-writing behavior, time zone, and all major failure modes. For a read-only export tool with an output schema, this is complete enough that an agent could invoke it correctly without further guidance.

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 that course_codes filters the schedule, which is useful, but does not clarify format expectations (e.g., exact code format like 'CS101'). Baseline 3 is appropriate given some meaning is added but the parameter remains under-specified.

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 (Build) and a precise resource (iCalendar .ics from the public OBS final exam schedule), and scopes it as filtered by course codes. Clearly distinguishable from siblings like export_course_schedule_ics and get_public_exam_schedule.

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 usage (no login required, public schedule) but does not explicitly state when to use this instead of get_public_exam_schedule or export_course_schedule_ics. The 'no login' hint gives context but no alternative routing.

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