List terms and academic calendar

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

Annotations already convey the read-only, idempotent, non-destructive profile. The description adds meaningful behavioral context beyond those annotations: it returns the current week of instruction, and with a term also returns academic calendar details such as instruction dates, finals week, and holidays.

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?

Three sentences, each earning its place: the first defines the core output, the second clarifies the optional behavior, and the third gives an explicit usage trigger. There is no filler or redundancy.

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 simple optional-parameter read-only tool, the description is complete: it states the data scope, the optional calendar behavior, the calendar contents, and when to call it. The safety profile is covered by annotations, and the return shape is self-evident from the description.

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?

The schema already fully documents the optional 'term' parameter, including a format example and the conditional calendar behavior. The description adds value by specifying what the calendar includes—instruction begins/ends, finals week, holidays—providing useful semantics beyond the schema.

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 uses a specific verb ('List') and resource ('UCI terms (quarters) that have schedule-of-classes data'), and adds the distinct secondary behavior of returning the current week and optional academic calendar. It is clearly differentiated from sibling tools like list_departments or search_courses.

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 gives an explicit invocation trigger: 'Call this first when the user says "next quarter" or doesn't name a term.' It provides clear context for when to use the tool, though it does not name alternatives or state when not to use it.

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