get_my_enrollments

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

Annotations already declare readOnlyHint=true, and the description adds meaningful context beyond that: the tool reads the user's own enrollments (not the roster), includes the user's role, and does not require roster-admin permissions. This clarifies access and scope assumptions.

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 tight sentences fully deliver purpose and usage guidance. No wasted words; front-loaded with the primary action. Each 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 read-only tool with an output schema and fully documented parameter, the description covers purpose, scope, and access context completely. Nothing critical is missing.

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 coverage is 100% with a clear description for the include_concluded parameter, so the schema carries the parameter meaning. The description does not add extra parameter details, but none are needed; baseline 3 applies.

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 ('List') and resource ('courses YOU are enrolled in'), and adds the detail 'with your role in each.' It explicitly distinguishes itself from sibling tool check_enrollment, making the purpose unmistakable.

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 direct when-to-use instruction: 'Use this — not check_enrollment — for any question about your own enrollment.' It explains why check_enrollment is not suitable (requires roster-admin rights the token likely lacks), providing clear exclusions and alternatives.

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