대학·학과 비교

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

With no annotations, the description carries full burden. It discloses the source (대학알리미) and comparison criteria, but does not explain behavioral aspects like handling missing data, output format, or what happens when majorName is omitted.

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?

Single sentence with parenthetical source note, no redundancy. Each element is essential and contributes to understanding.

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 no output schema, the description does not explain return values or format. It covers the core purpose but omits details on output structure or limitations, especially regarding the optional majorName parameter.

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 covers 50% (universities described as 2~4 universities). Description adds meaning by indicating the comparison is for the same department across universities, clarifying the role of majorName, which is otherwise undocumented.

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?

Description clearly states the tool compares multiple universities by competition rate, tuition, scholarships, and employment rate, and evaluates cost-effectiveness. It distinguishes from sibling tools like search_university or get_major by specifying the comparison function.

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?

Description implies usage for comparing universities on given metrics but provides no explicit guidance on when to use this tool over alternatives, nor exclusions. It lacks when-to-use/when-not-to-use context.

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