Chosun Course Offerings

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

No annotations exist, so the description must fully convey behavioral traits. It only says 'Search', implying read-only, but fails to clarify side effects, result limits, caching, or error handling. For a tool with 15 parameters and no output schema, this is insufficient.

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 extremely concise (one short sentence), front-loaded, and without fluff. However, for a complex tool, it sacrifices essential context, making it too minimal to earn a higher score.

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 15 parameters, no output schema, and no annotations, the description should provide more context about return format, pagination, default behaviors, and failure modes. It falls short, leaving the agent with an incomplete picture.

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 87% (high), so the schema explains most parameters. The description adds no additional parameter meaning, but since the schema is already rich, a score of 3 (baseline) is appropriate.

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 'Search undergraduate course offerings', specifying the verb 'Search' and resource 'course offerings'. It distinguishes itself from sibling tools like chosun_course_syllabus (syllabus for a specific course) and chosun_timetable (personal schedule) by focusing on available offerings.

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 no guidance on when to use this tool versus alternatives like chosun_course_syllabus or chosun_graduation_diagnosis. It lacks context for typical use cases, prerequisites, or exclusion criteria, leaving the agent to infer from the tool name alone.

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