get_grades

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

Annotations only include readOnlyHint=true, so the description adds useful behavior: grades show 'NA' until posted, omitting `term` returns the current semester, and `available_terms` in the response lists other queryable terms. This goes beyond the annotation and helps set expectations.

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?

Three sentences with no redundancy: the first defines output, the second gives usage conditions, and the third covers behavioral nuances. The most important scoping information is front-loaded.

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?

Given the low parameter count, the output schema, and the readOnly annotation, this is nearly complete. The only notable gap is the undocumented `force_refresh` parameter, which prevents a 5.

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 description coverage is 0%, so the description must compensate. It does explain `term` well ('Omit `term` for the current semester; `available_terms` in the response lists what else can be queried'), but it says nothing about `force_refresh`. The parameter name and default are weakly indicative, but an explicit explanation would be needed for full clarity.

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 a specific verb and resource: it returns grades for one semester, including per-course grade options, units, mid-semester and final grades, and QPA summaries. It is distinct from sibling tools like get_schedule or get_advanced_placement by explicitly naming the grading/QPA domain.

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 explicit direction: 'Call this when the user asks about grades, QPA/GPA, or units for a semester.' It does not name specific alternatives or state when not to use it, but the context is clear enough for an agent to route correctly.

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