get_today_classes

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

Adds substantial behavioral context beyond annotations: returns a holiday/no-class result on non-instructional days, follows working-Saturday day-order rules, and specifies the NOT_AUTHENTICATED recovery sequence (get_captcha → login → retry). These are non-obvious runtime behaviors an agent must know.

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-loads the primary purpose, then layers calendar edge cases and auth recovery in a compact run of sentences. Slightly dense but every clause carries information; no filler.

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?

For a single-param read tool with no output schema, the description covers purpose, edge cases (holidays, working Saturdays), auth failure handling, and parameter usage. Nothing an agent needs is missing.

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 coverage is 100%, so the baseline is 3, but the description clarifies the format ('ISO YYYY-MM-DD') and adds the default behavior ('or a given date', 'today'), marginally enriching what the schema already states.

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 (list) and resource (classes scheduled for today) with scope qualifiers including time and venue. Distinguishes itself from the sibling get_timetable by being date-scoped ('today') rather than a general timetable.

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?

Clear context for when to use (today's classes, or another day via the date param) and explains the auth-recovery flow. Does not explicitly contrast with get_timetable, but the 'today' framing makes the intended use case obvious.

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