kupid_get_timetable

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

With no annotations provided, the description carries the full burden. It discloses an authentication requirement (SSO login) and the data source (portal widget), implying a read operation. However, it does not mention potential rate limits, caching behavior, or whether it modifies any state.

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 sentences for purpose and two bullet points for parameters. It front-loads the core action and then provides details, with no unnecessary words.

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 tool's simplicity (optional parameters, output schema exists), the description adequately covers the authentication requirement, parameter options, and data source. It could optionally mention default behavior of day or whether ics_export is file content or URL, but overall it is sufficient.

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 fully compensates by explaining the day parameter values ('all', 'mon', etc.) and the effect of ics_export (returns ICS file content if True). This adds significant meaning beyond the bare schema.

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 '개인 수업시간표를 조회합니다' (retrieve personal class timetable), which is specific verb+resource. However, it does not explicitly differentiate from the many sibling tools, though it's distinguishable by the 'timetable' resource.

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 login is required and that it parses data from the portal main page timetable widget, but does not provide explicit guidance on when to use this tool versus alternatives or 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.