Get My Courses

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

Annotations declare readOnlyHint: true, which already indicates a safe read operation. The description adds the 'active' filter and 'authenticated student' scope, but does not disclose behaviors like result ordering, pagination, or potential incomplete data (despite openWorldHint). It adds some value but leaves gaps.

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, front-loaded sentence with no fluff. It conveys the essential purpose without unnecessary detail.

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?

With no output schema, the description should clarify what the returned courses look like (e.g., course objects with fields). It only says 'list active courses', which implies a list but gives no information about the structure or content. Given the low complexity and existing annotations, it is minimally complete but could be clearer.

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 are no parameters, so the description has nothing to add beyond the schema. Baseline of 4 is appropriate for zero parameters, and the description does not need to explain any input semantics.

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: listing active courses for the authenticated student. It uses a specific verb ('list') and resource ('courses'), and the scope ('authenticated student', 'active') distinguishes it from siblings like list_courses or get_course.

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 provides clear context: it is for the authenticated student's own active courses. However, it does not mention alternatives or explicitly state when not to use this tool, which would be helpful given the many course-related siblings.

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