list_semesters

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

The description adds useful behavioral caveats beyond the annotations: past semesters are archived and future semesters beyond one term are usually empty. This is valuable expectation-setting for a read-only tool and does not contradict the readOnlyHint.

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 short, front-loaded with the essential purpose, and has no filler. Every sentence adds useful information: the first gives the core purpose, the second explains relevant behavioral edge cases.

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 0-parameter list tool with an output schema, the description is nearly complete: it explains the purpose, current-semester semantics, and the caveats around archived/empty semesters. The only minor gap is that it does not specify how the current semester is determined, but that is not needed to call the tool.

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 tool has zero parameters and schema coverage is 100%, so there is no parameter documentation burden. The description provides helpful context about semester codes and current/empty states, which more than satisfies the baseline for a no-parameter tool.

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 clearly states that the tool tells the agent which semester codes to use and which one is current, naming the resource 'semesters' and the two key questions. It is distinct from sibling tools like search_courses or list_departments, though it lacks an explicit verb like 'lists'.

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 clear usage context: use this to understand semester codes and identify the current term. It also warns about archived past semesters and usually-empty future ones, which helps the agent decide when to query those semesters. It does not explicitly name alternatives, so it misses full when-not guidance.

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