get_enrollments

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

Discloses that the tool returns grades and enrollment items for the current user, adding context beyond the tool name. However, no annotations exist, and the description does not address authentication, rate limits, or other behavioral aspects.

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?

Extremely concise: two sentences with no wasted words. Purpose and return value are stated upfront.

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?

Provides the essential information for a no-parameter tool: what it does (get enrollments with grades) and what it returns (Dict with enrollment items). Could include details like filtering or scope (e.g., only active enrollments), but it is adequate.

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?

No parameters are present, and schema coverage is 100%. The description does not need to explain parameters. Baseline for no-parameter tools is 4.

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?

Clearly states the action ('Get') and resource ('enrollments'), specifying it is for the current user and includes grades. This distinguishes it from sibling tools like list_courses or list_assignments, which return different 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?

No guidance on when to use this tool versus alternatives like list_courses or get_course. Does not describe prerequisites, context, or exclusions.

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