share_list_my_courses

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

Annotations already state that the tool is read-only, idempotent, non-destructive, and open-world. The description adds useful scope by saying the result includes courses, teaching classes, and teachers, but it does not explain authentication requirements, pagination, or output behavior beyond what the annotations and output schema provide.

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 short sentences with no wasted text. The main action is front-loaded, and the semester caveat is appended efficiently.

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?

The tool is a simple read-only list operation with annotations and an output schema, so the description does not need to explain return values. However, because both input parameters lack schema descriptions, the description should do more to explain the expected year format and semester constraints to be fully 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?

Schema description coverage is 0% for the two required parameters. The description partially clarifies semester by saying it is usually 1/2/3 and should follow the user's semester interface, but it gives no format or meaning for the year parameter and leaves year semantics largely undocumented.

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 and resource: listing the user's courses, teaching classes, and teachers by academic year and semester. It is clear enough to distinguish the tool from broader course search tools, but it does not explicitly name the sibling alternatives such as share_search_courses or share_list_course_classes.

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?

Usage is implied by the name and description: call this when you need the user's own courses for a given year and semester. The description adds guidance about semester values, but it does not state when not to use this tool or point to an alternative sibling tool.

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