ncloud_get_extended_status

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

The description is consistent with the readOnlyHint annotation, and it adds the resource context (Extended Metric collection status). However, it does not disclose additional behavioral details such as what the status values mean, whether filtering is applied, or any response format nuances. Given the annotation already declares a safe read operation, this is a baseline acceptable disclosure but not rich.

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, focused sentence with no redundant or irrelevant content. It efficiently communicates the tool's purpose without wasting tokens.

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 simple read operation with two well-described parameters and no output schema, the description provides adequate context on what the tool returns ('Extended Metric collection status'). However, it does not explain what 'status' entails or how to interpret the response, leaving some ambiguity for an agent unfamiliar with Cloud Insight. Still, for a getter of this simplicity, it is minimally sufficient.

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 provides complete descriptions for both parameters: prodKey as 'Product key (cw_key)' and servers as 'Server instance numbers to check.' The description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate since the schema covers all parameters.

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 the specific verb 'Get' with a clear resource: 'Extended Metric collection status for servers in Cloud Insight.' It identifies the domain (Cloud Insight) and scope (servers), distinguishing it from generic monitoring tools. However, it does not explicitly differentiate from sibling tools like ncloud_query_monitoring_data or ncloud_search_metric_list, so it falls short of a 5.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or related tools. The description only states what the tool does, leaving the agent to infer usage context from the name and schema.

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