kupid_search_courses

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

With no annotations, the description carries full burden. It discloses the special behavior of returning college list when college is empty and mentions SSO requirement. However, it does not state whether the tool is read-only, describe any side effects, or address rate limits or data freshness.

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 well-structured: a clear purpose line, a scope line, a special behavior note, and a parameter table. It is not overly verbose, though the parameter explanations could be slightly more concise without losing clarity.

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 covers all parameters, special behavior, and auth requirement. Output schema exists, so return values need not be explained. However, it lacks details on error handling, pagination, or performance characteristics.

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?

Despite 0% schema description coverage, the description's Args section provides detailed semantics for all 6 parameters, including defaults, examples for college and department codes, and enum values for semester and campus. This fully compensates for the lack of schema descriptions.

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 searches for offered courses and returns a college list when college code is empty. It distinguishes itself from sibling tools like kupid_my_courses (user-specific) and kupid_get_syllabus (specific course). However, it does not explicitly differentiate from similar search tools like kupid_search.

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 notes SSO login is required and explains the special case of empty college code. However, it provides no guidance on when to use this tool versus alternatives (e.g., kupid_my_courses, kupid_get_syllabus), nor does it mention when not to use it.

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