list_enrollments

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

No annotations provided, so the description carries full responsibility. It does not disclose behavioral traits such as authentication requirements, scope (current user only?), or default behavior when parameters are omitted. Only implicitly indicates it returns a list with specific fields.

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 very short (one sentence) but under-specified. It front-loads the resource name but omits critical action and usage details. Conciseness is not beneficial when key information is missing.

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 two optional parameters and an output schema, the description should clarify scope (which student? default semester?). It does not address how parameters affect results or what to expect when they are absent. Incomplete for a tool with multiple list siblings.

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% (no descriptions for parameters). The description adds no meaning beyond the schema for 'source' or 'semester_id'. It fails to explain what these parameters control, e.g., manual vs USP source, or how semester_id filters results.

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 identifies the resource (enrollments) and mentions included details (meetings, professor, credits), but lacks a verb and is phrased as a noun phrase. It does not explicitly state 'list' or 'retrieve', though the tool name clarifies. Sibling tools like list_absences and list_grades imply similar patterns, but the description does not differentiate this from get_schedule or other listing tools.

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?

No guidance on when to use this tool versus alternatives. Does not specify whether it returns data for the current student or requires authentication. No exclusions or context for parameter use (e.g., semester_id vs current).

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