Public Active Term

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that no login is required and clarifies what 'active' means by contrasting with registration's current term. However, it does not explain potential behaviors around the level parameter, whether the result can be empty, or how stable 'usually' is.

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?

Two sentences with no filler. The first sentence states the action and result; the second adds a key caveat and auth hint. Information is front-loaded and every sentence earns its place.

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 simple one-parameter public lookup, the description covers purpose, auth, and category distinction, and an output schema exists. The significant missing piece is the unexplained 'level' parameter, which prevents the definition from being fully self-sufficient.

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 input schema has one optional parameter, 'level', with default 'LS', and 0% schema description coverage. The description never mentions this parameter, so an agent cannot know what values are valid, whether it changes the returned term, or what 'LS' means.

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 states a specific verb and resource: 'Return the term whose course schedule is currently published on the public OBS pages, with its term code.' It also distinguishes itself from the registration-current term, which separates it from the sibling tool obs_public_registration_term.

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 context: it is for the publicly published schedule term, usually the upcoming term, and explicitly says no login is required. It does not name an alternative tool or explicitly state 'use this when…', so it falls just short of full usage guidance.

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