get_student_context

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

The annotations already declare readOnlyHint=true, so the description does not need to restate that this is a safe read operation. The description adds useful context that the current semester can be reused as a term argument elsewhere, but it does not disclose edge cases such as missing or stale data. This is sufficient given the annotation coverage.

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 two concise sentences with no redundant wording. The core purpose and data fields are front-loaded, followed by a clear usage directive. 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 no-parameter, read-only tool with an output schema, the description fully covers what data is returned and when to invoke the tool. It also explains how the output can be used in downstream calls, making it complete for correct invocation.

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 the input schema is empty, so there is nothing to document. The description appropriately references 'term' as an output value to be reused, which is helpful context beyond the schema. Baseline 4 applies for zero-parameter tools.

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 identifies the tool's purpose: retrieving a current snapshot of the student's academic context, with a concrete list of fields such as name, term, class level, major, and advisor. This specificity distinguishes it from sibling tools like get_schedule and get_grades, which target different academic data.

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 provides strong usage guidance: 'Call this first in any conversation touching academics' and 'whenever you need the current semester to pass as a term argument elsewhere.' However, it does not explicitly discuss when to use sibling tools instead, so it lacks exclusions.

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