get_calendar

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

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: it requires login, discloses the NOT_AUTHENTICATED recovery flow, and explains the semester-scoping behavior of festivals (with a fallback to get_semesters). This is meaningful operational context an agent needs.

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 core purpose, then the parameter guidance, then the fallback/auth caveats in priority order. It is information-dense and free of filler, though the long multi-clause sentences are slightly run-on.

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 still covers defaults, parameter intent, semester-scoping edge cases, and the auth error path. An agent has everything required to call it correctly and recover from the common failure modes.

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 adds genuine semantic value: it explains the default behavior with no filter, how query/month/holidaysOnly differ in intent, and why semesterId may be needed to locate a term-bound event.

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 ('Look up the academic calendar') and enumerates exactly what it contains: holidays, events, working Saturdays/day-orders, and instructional days. This scope is clearly distinguishable from siblings like get_timetable or get_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?

Explicitly maps each parameter to an intent (query for named events, month for a month listing, holidaysOnly for no-class days) and describes the no-filter default. It also names concrete alternatives and recovery paths: get_semesters when a query finds nothing, and get_captcha/login on NOT_AUTHENTICATED.

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