ncloud_get_public_ip_target_servers

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

Annotations declare readOnlyHint=true, and the description aligns by stating 'List server instances'. There are no contradictions, but the description does not disclose additional behavioral traits like eligibility criteria, return format, or edge cases beyond a simple listing.

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?

One concise sentence, front-loaded with verb and resource. Every word is meaningful; no fluff.

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 parameterless listing tool with readOnlyHint annotation, the description is sufficiently complete. It clearly states the tool's function. Could potentially clarify 'eligible' criteria (e.g., region, status) but overall meets needs.

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?

Input schema has zero parameters, so no parameter descriptions are needed. Schema coverage is 100%. Baseline score for 0 parameters is 4, and description adds no extra param info, which is acceptable.

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 'List server instances that can be assigned a public IP', specifying the verb (list), resource (server instances), and purpose (eligible for public IP). It distinguishes itself from sibling tools like ncloud_list_servers and ncloud_get_public_ip_detail.

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?

No guidance on when to use this tool versus alternatives (e.g., ncloud_list_servers). No mention of prerequisites, dependencies, or context for choosing this tool over others.

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