kupid_get_all_grades

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

No annotations are provided, so the description carries the full burden. It discloses the authentication requirement and that it fetches finalized grades from a specific screen. It does not mention rate limits or data freshness, but for a read-only operation this is acceptable.

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 with two short paragraphs. It front-loads the purpose, then provides context and parameter details. Every sentence adds value with no redundancy.

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, the description adequately covers the tool's function, preconditions (SSO login), and parameter usage. It misses potential details like whether the data is cached or if there are pagination limits, but these are not critical for a simple list tool.

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%, but the description includes an Args section explaining the parameter: 'year_term: 조회할 학년도/학기 코드 (예: "20242R"). 비우면 전체 조회'. This adds semantic meaning beyond the schema, clarifying the format and default behavior.

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 it retrieves all grades, cumulative GPA, and earned credits. It specifies the source ('KUPID 학적/졸업 > 성적사항 > 전체성적조회 화면') and distinguishes from sibling tools by focusing on overall grades versus course-specific grades (e.g., kupid_lms_grades).

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 mentions 'SSO 로그인 필요' indicating a prerequisite. It provides an example for the parameter and implies when to use (for overall grades) but does not explicitly state when not to use or compare to alternatives.

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