list_my_courses

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

No annotations are provided, so the description must stand alone. It states what the tool does but does not disclose behaviors like whether hidden courses are included by default (only_visible defaults to false in the schema), pagination, or rate limits. The schema provides some parameter details, but the description itself is minimal and does not add behavioral context.

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 a single sentence with no wasted words. It front-loads the purpose and includes a useful parenthetical, making it both concise and well-structured.

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 description is sufficient for a simple listing tool, but it lacks details on return structure, pagination, and the meaning of limit. Since there is no output schema and annotations are absent, the description could be more informative to fully guide an agent.

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?

The description adds a note on userid sources ('obtain from get_site_info for the bot, or pass a student_id-mapped Moodle userid'), which supplements the schema's userid description. However, it does not explain the limit parameter at all, and only_visible is already described in the schema. With schema coverage at 67%, the description provides partial added value.

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 clearly states the tool's function: 'List courses where a user is enrolled.' The verb 'list' and resource 'courses' are specific, and the scope (for a given userid) distinguishes it from sibling tools like list_students or get_course_context.

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 clear context on when to use the tool by specifying it lists courses for a specific user, and provides a useful hint on obtaining the userid from get_site_info. It doesn't explicitly name alternatives or state when not to use it, so it stops short of a 5.

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