ncloud_get_servers_top

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that the tool returns only the top 5 servers and that it uses monitoring data from Cloud Insight. This provides useful context beyond the annotation, though it lacks details on data freshness or return format.

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, well-structured sentence of 17 words. It is front-loaded with the action and resource, and every word provides value. No unnecessary information.

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 (1 parameter, no output schema, read-only), the description adequately explains what the tool does: returns the top 5 servers by specified metric. However, it does not hint at the output format (e.g., server IDs, usage percentages), which would be helpful for an agent. Still, it is largely complete for its complexity.

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 input schema has 100% description coverage for the single parameter 'metricType', including enum values. The description merely restates the parameter's purpose without adding new meaning. Baseline score of 3 is appropriate.

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 uses a specific verb ('Get'), resource ('servers'), and scope ('top 5 by CPU, memory, or filesystem usage'). It clearly distinguishes from siblings like ncloud_list_servers (which lists all servers) and ncloud_get_server_detail (which retrieves detail for one server), as it focuses on top-ranked servers by monitoring metrics.

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 states the tool retrieves top servers 'from Cloud Insight monitoring,' providing context. However, it does not explicitly state when to use this tool over alternatives like ncloud_query_monitoring_data, nor does it mention when not to use it (e.g., if a full list or detailed info is needed).

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