get_semester_info

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

Beyond the read-only/idempotent annotations, it discloses the important domain behavior that when teachingOver is true attendance is locked/final rather than projectable, and that login is required. This is non-obvious semantic context an agent cannot get from the annotations or schema.

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?

Field list is front-loaded, followed by the teachingOver caveat and usage questions. Three sentences that each carry information, with no filler. Slight redundancy in restating return fields, but efficient overall.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so thoroughly (all fields listed plus the locking semantics). Combined with the auth requirement note, an agent has everything needed to call and interpret this 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?

Schema coverage is 100% and both parameters (refresh cache behavior, semesterId defaulting to current) are fully documented in the schema itself. The description adds no parameter-level detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 gives a specific resource (semester term bounds) and enumerates the exact fields returned: id, name, first/last instructional day, totals, days remaining, teaching-over flag. This is far more concrete than a tautology. It does not explicitly name how it differs from siblings like get_semesters or get_calendar, so it falls short of a 5.

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?

It gives explicit user-facing questions this answers ('when does my semester end?', 'how many teaching days are left?'), which is clear usage context. However it does not name the alternative tools (e.g. get_calendar or get_semesters) or state when-not to use it, so it does not reach a 5.

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