벨로그 로그인

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

The description discloses that the tool requires user interaction in the browser, that it saves a profile for future use, and that headless=True enables windowless renewal. This adds significant behavioral context beyond the annotations (readOnlyHint=false, openWorldHint=true).

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 three sentences, each serving a clear purpose: purpose statement, usage trigger, and login flow explanation. No unnecessary words, well-front-loaded.

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?

For a login tool, the description covers purpose, usage trigger, and behavioral details. It does not mention error handling for login failures, but the timeout parameter addresses waiting. Overall, it is fairly complete given the output schema exists.

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 coverage is 100%, so each parameter is already described. The description adds value by integrating the parameters into a workflow: explaining when headless should be false (first login) and when it can be true (renewal). This provides semantic context beyond individual parameter descriptions.

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 that the tool opens a Velog login window to obtain and save a token. It distinguishes its purpose from sibling tools by specifying it handles authentication for write 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 explicitly says to call this tool when write tools give authentication errors. It also distinguishes between first login (headless=False) and subsequent renewals (headless=True), providing clear usage guidance.

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