kupid_my_courses

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

No annotations are provided, so the description carries full burden. It discloses that SSO login is required, which is a behavioral constraint. However, it does not discuss error handling, side effects, rate limits, or what happens if no courses are found. The read-only nature is implied but not explicitly stated.

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 concise and front-loaded with the core purpose. The Args section is clear and well-structured. A minor improvement would be integrating the Args into a more natural paragraph, but overall it is efficient with no unnecessary text.

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?

Given the presence of an output schema (not shown, but indicated), the description appropriately focuses on parameters and usage context. It covers login requirement, parameter details, and returned fields. Missing elements include no result handling or edge cases, but for a simple retrieval tool, it is largely 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%, so the description adds significant value. It explains that year defaults to the current semester and semester accepts specific values ('1', '2', 'summer', 'winter'). This goes well beyond the schema which only has string type with empty defaults.

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 retrieves the user's course registration details, specifies that SSO login is required, and lists the returned information (course number, time, classroom, professor, credits, etc.). This distinguishes it from sibling tools like kupid_search_courses (which searches courses) or kupid_get_timetable (which shows schedule).

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 a prerequisite (SSO login) and default values for parameters, but does not explicitly compare to sibling tools or state when to use this tool vs alternatives. The context is clear but lacks exclusions or explicit guidance.

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