Public Course Schedule

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully discloses that no login is required and that this is a public read-only lookup, but it does not describe how the optional filters (day, level, instructor, course_code, only_available) affect the result set, nor what happens with empty results or invalid branches.

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?

The description is one efficient sentence with the main action front-loaded, concrete output fields, and an authentication note. There is no filler or redundant restatement of the title.

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?

Given six parameters, zero schema descriptions, and no annotations, the description is incomplete for reliable invocation. It does not explain the filter parameters, the default level behavior, or how to obtain a valid branch value, although the output schema may cover return-structure details.

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 for undocumented parameters. It only clarifies the required branch parameter via 'for a course branch'; the five optional filter parameters are left entirely to the agent to infer from their names and defaults.

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?

Clearly states a specific action: return every published section for a course branch, and enumerates the expected fields (CRN, meeting days/times, instructor, room, quota, remaining seats). 'No login required' also helps distinguish it from authenticated schedule tools such as obs_get_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 'No login required' note gives clear context for when to use this public endpoint versus authenticated schedule tools. However, it does not explicitly name an alternative or state when not to use it, such as when an individual user's enrolled schedule is needed.

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