ncloud_wms_get_results

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

The description merely restates that this is a read operation ('Get'), which is consistent with readOnlyHint=true, but adds no behavioral context beyond that. It does not disclose return format, aggregation behavior, filtering semantics, pagination, or rate limits, providing little value beyond the annotation.

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?

A single concise sentence that directly states the tool's purpose with no filler, redundancy, or irrelevant detail.

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 6 parameters, 2 enums, and no output schema, the one-sentence description is insufficient. It does not explain what the returned monitoring results contain, how aggregation types work, or how to distinguish this from ncloud_wms_get_result_detail. The rich schema descriptions partially compensate, but the description lacks essential context.

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 already describes all 6 parameters with 100% coverage, including enums for type and resultStatus. The description's mention of 'WMS scenario' and 'time range' only echoes schema fields and adds no new parameter semantics.

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 tool retrieves monitoring results for a WMS scenario over a time range. The plural 'results' and domain scope differentiate it from sibling tools like ncloud_wms_get_result_detail, which focuses on a single result 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 explicit guidance is given on when to use this tool versus alternatives such as ncloud_wms_get_result_detail or ncloud_wms_get_monitor. The phrase 'over a time range' weakly implies a time-bounded query, but there are no exclusions or alternative recommendations.

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