kupid_login

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

No annotations are provided, so the description carries full burden. It discloses that it logs in, checks session, and reuses cached sessions. However, it does not detail behavior on invalid credentials, error handling, or whether the tool is idempotent. Moderate transparency.

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?

Three sentences, no filler. The purpose is stated first, followed by requirements and behavior. Extremely concise and well-structured.

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 there are no parameters and an output schema exists, the description is mostly complete. It could mention what the output provides (e.g., session token), but this is covered by the output schema. Sibling context makes it clear this is a prerequisite 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?

There are no parameters, so the schema coverage is complete (100%). The description does not need to add parameter semantics, and it does not. Baseline score of 4 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 the tool's function: logging in to KUPID portal and checking session. It uses a specific verb ('로그인하고') and resource ('KUPID 포털'), and effectively distinguishes itself from sibling tools, which are all specific data retrieval or action tools.

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 prerequisite environment variables and session caching, but does not explicitly state when to use this tool versus its siblings. It is implied that it should be called before other kupid tools, but this guidance is not direct.

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