Naver Mail MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. '서버 상태 확인' implies a read-only diagnostic operation, but it doesn't specify what 'status' means (e.g., connectivity, health metrics, uptime), whether authentication is required, potential rate limits, or what the output format might be. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 a single, efficient phrase ('서버 상태 확인') that communicates the core purpose with zero wasted words. It's appropriately sized for a simple diagnostic tool and is front-loaded with the essential information. Every element of the description earns its place.

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 (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks behavioral context and usage guidance. For a diagnostic tool that likely returns status information, the absence of output schema means the description should ideally hint at return values, but the basic purpose statement is adequate for the simplest use cases.

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 has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to compensate for any parameter documentation gaps. The baseline for zero parameters with complete schema coverage is 4, as there are no parameters whose semantics need explanation beyond what the structured schema already provides.

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 '서버 상태 확인' (server status check) clearly states what the tool does with a specific verb ('확인' - check) and resource ('서버 상태' - server status). It distinguishes from all sibling tools which are mail/folder management operations, making the purpose unambiguous. It doesn't specify the exact mechanism (e.g., ping response time, health endpoint) but provides adequate clarity for a simple diagnostic tool.

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 provides no guidance on when to use this tool versus alternatives. There are no explicit instructions about when this tool is appropriate, what prerequisites might exist, or what context warrants its use. The agent must infer usage from the purpose alone, which is insufficient for optimal tool selection.

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