get_my_enrollments

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

Annotations already indicate readOnlyHint=true, and the description adds context that the tool returns the user's role per course. No contradiction. Although it doesn't mention pagination or error scenarios, the read-only nature is clear and annotations lower the burden. The extra detail about roles adds value.

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 sentences, front-loaded with the primary purpose and followed by concise usage guidance. No wasted words.

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 list tool with no output schema, the description indicates what is returned (courses with roles) and provides essential usage context. It doesn't detail output fields or pagination, but given the read-only annotation and simple schema, it is reasonably complete.

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?

There is only one parameter (include_concluded) and the schema provides full coverage (100%) with a clear description. The tool description does not add further parameter details, but the schema already explains the default and behavior, so the baseline of 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') plus the extra scope of 'with your role in each.' It clearly distinguishes from the sibling tool check_enrollment, which reads the roster for others.

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 explicitly instructs to use this tool instead of check_enrollment for own-enrollment queries, and explains why check_enrollment is unsuitable (requires admin rights). This is explicit when-to-use and when-not-to-use guidance.

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