get_course

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful scope context by saying it returns *every* index with a *complete* timetable (a broad, full-expansion read rather than a paginated summary), but says nothing about authentication, rate limits, or behavior when the course/year/semester combination does not exist.

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?

A single front-loaded sentence with zero filler. The returned scope is stated up front, so an agent can triage the tool in one read.

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?

An output schema exists, so return values need not be explained, and the description does convey what the tool fetches. It is nevertheless incomplete for a 3-required-parameter tool whose parameters carry no documentation at all, particularly the ambiguous semester enum.

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%: none of course_code, academic_year, or semester is documented anywhere. The description only vaguely implies a course identifier is involved and adds nothing about the semester enum values (1, 2, 'S'), which are especially cryptic without explanation.

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 ('Get course metadata and every index with its complete timetable'), which is clearer than a bare 'get course'. However it never differentiates itself from the sibling get_course_indexes or get_index_schedule, so an agent must infer which of the two overlapping-sounding tools to call.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. With siblings like get_course_indexes and get_index_schedule that plausibly overlap, the absence of routing guidance is a real gap.

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