ncloud_query_monitoring_data_multiple

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description's job is to add context, and it does supply the batch ceiling of 20 conditions. Beyond that it says nothing about return format, data-point limits, retention windows, or rate limits for a monitoring query.

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 sentence with the scope constraint front-loaded and no filler words. The parenthetical carries real information (batch cap) rather than padding.

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 read-only query with a fully documented nested schema and a safety annotation, the core is covered. However, with no output schema the agent gets no hint of the response shape (series structure, aggregation of results, partial-failure behavior when some of the 20 conditions are invalid), which is a real gap for a batch API.

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?

Schema description coverage is 100%, and the nested metricInfoList fields (metric, prodKey, interval enum, dimensions, aggregations) are fully documented in the schema itself. The description's only parameter-adjacent detail, the 20-condition cap, merely restates maxItems=20, so it adds no meaning beyond the schema.

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?

Names a specific verb and resource ('Query ... monitoring data from Cloud Insight') and states the scope precisely: multiple time-series in one request, capped at 20 metric conditions. It implicitly separates itself from the singular sibling ncloud_query_monitoring_data via 'multiple', but never names that sibling explicitly.

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?

Usage is only implied by 'multiple ... in a single request', which suggests batching several metrics rather than issuing several single-metric calls. There is no explicit when-to-use statement, no exclusion conditions, and no reference to the sibling query tool as the alternative for single-metric lookups.

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