NHN Server MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('reload server configuration') and context of use, but doesn't describe what 'reload' entails behaviorally - whether it requires specific permissions, if it interrupts service, what happens on failure, or what the response looks like. The description adds basic context but lacks detailed behavioral traits.

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 perfectly concise with two sentences that each earn their place: the first states the core action, the second provides usage context. It's front-loaded with the primary purpose and wastes no words. The Korean language doesn't affect conciseness scoring.

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 has no parameters (simple interface) and no output schema, the description provides adequate but minimal context. It explains what the tool does and when to use it, but doesn't address what happens during execution, potential side effects, or what constitutes success/failure. For a configuration reload operation with no annotations, more behavioral context would be helpful.

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, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, and the baseline for 0 parameters is 4. No additional parameter semantics are needed or provided.

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 verb ('reload') and resource ('server configuration'), making the purpose specific and understandable. It distinguishes from siblings by focusing on configuration reloading rather than status checking, connection management, or command execution. However, it doesn't explicitly differentiate from 'get_config' which might retrieve configuration without reloading.

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 clear context for when to use the tool ('when SERVER_INFO_FILE etc. have been changed'), giving practical guidance. It doesn't explicitly state when NOT to use it or name alternatives among siblings, but the context implies it's for applying configuration changes rather than general operations.

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