ncloud_query_widget_preview

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

The description implies a read operation (query) consistent with the readOnlyHint annotation, but adds no additional behavioral context such as performance characteristics, data freshness, or required permissions. The annotation relieves some burden, yet the description remains shallow.

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 extremely concise (one sentence) and includes the key purpose. It is front-loaded and clear, but could be better structured to include key details like return type or usage notes.

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 7 parameters, no output schema, and many sibling query tools, the description is incomplete. It does not explain what 'widget preview data' comprises, what the tool returns, or how it differs from ncloud_query_monitoring_data or ncloud_get_dashboard_widgets. This leaves the agent with significant uncertainty.

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%, so the schema already documents all parameters. The description hints at the metric parameter but adds no deeper semantics (e.g., format, constraints, or how dimensions interact). No value 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?

The description clearly states it queries widget preview data from Cloud Insight by specifying metrics, which is a specific verb-resource combination. However, it does not differentiate from sibling tools like ncloud_query_monitoring_data or ncloud_get_dashboard_widgets, missing a chance to clarify its unique role.

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, limitations, or scenarios where other tools (e.g., ncloud_query_monitoring_data) would be more appropriate.

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