ncloud_query_widget_preview

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

Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds that data comes from Cloud Insight and that metrics are supplied directly, which is useful framing, but it says nothing about auth requirements, result size, or aggregation behavior beyond what the schema's enums already convey.

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 front-loaded sentence with no filler; the purpose and the metric-driven approach come first. It is efficient, though perhaps too sparse for a tool with a complex nested metricsInfo array.

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?

With annotations covering safety and a fully documented schema, the core need is met. But for a query tool with no output schema and a nested metric-definition array, the description gives no sense of what the preview returns or how multiple metrics are combined, leaving a gap.

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% with richly documented nested fields (metric, prodKey, statistic, period, dimensions), so the schema does the heavy lifting. The description's only parameter-relevant contribution is 'specifying metrics directly,' which does not add 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?

States a specific verb (Query) and resource (widget preview chart data from Cloud Insight) with the key distinguishing detail that metrics are specified directly. However, it doesn't name or contrast with the many nearby monitoring siblings (ncloud_query_monitoring_data, ncloud_get_dashboard_widgets, ncloud_get_dashboard_widget_image), so an agent gets the purpose but no sibling differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance. 'By specifying metrics directly' implies a contrast with a widget-ID-based fetch, but no alternative tool is named and no prerequisites or context are given. This leaves routing entirely to inference.

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