get_semesters

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

Discloses non-obvious ordering: VTOP returns semesters newest-first, index 0 is current, index 1 is the most recent completed term, and the last element is the oldest. It also warns that taking the last element silently returns the student's first semester and documents structured error handling via structuredContent.error.code.

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 front-loaded with the tool's purpose, then immediately gives the critical ordering caveat, usage guidance, and error recovery. Every sentence provides operational value for correct invocation or interpretation.

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 and no parameters, the description fully covers return contents, ordering, defaulting behavior of related tools, and authentication error recovery. An agent has enough information to call this correctly and interpret the result safely.

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?

There are no input parameters, so the baseline is 4. The description appropriately does not invent parameter semantics, though it notes the response carries id and name.

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 list of available semesters', with output shape '(id + name)'. It also distinguishes its scope from other data tools that default to the current semester when semesterId is omitted.

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 says most data tools default to the current semester, so 'you usually don't need to call this unless the user asks about a specific past semester.' It also gives a concrete recovery path for NOT_AUTHENTICATED errors.

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