setup_naver_mail

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

Beyond the annotations (which only mark it as non-read-only, idempotent, non-destructive, closed-world), the description discloses the local-only binding (127.0.0.1), that a browser page is opened for the user, that the page URL is returned, and a security constraint: never ask the user to type the password in chat.

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, all load-bearing: what it does, when to call it, and the security rule. The local-only scoping detail is front-loaded where an agent will read it first.

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?

There is no output schema, but the description explicitly states the return value ('Returns the page URL'), and it covers the trigger conditions, the local-only constraint, and the password-handling rule. Nothing an agent needs to invoke this correctly is missing.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly frames the interaction as happening in the browser page rather than through arguments, which reinforces that no input is expected.

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 states a specific verb and resource ('Open a local setup page ... where they enter their NAVER address and application password') and scopes it precisely to 127.0.0.1/this computer only. This is clearly distinguishable from read-oriented siblings like list_mailboxes or send_email.

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?

It gives explicit triggering conditions: when the user asks to set up, connect, or change their NAVER mail account, or when another tool returns NOT_CONFIGURED. That covers both direct user intent and an error-driven fallback path, leaving nothing to inference.

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