ncloud_get_dashboard_widgets

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

The readOnlyHint annotation already discloses the read-only safety profile, and the description adds the scoping constraint that the operation is for a specific dashboard, not global. However, it does not add behavioral details such as return format, pagination, or required permissions, but given the low complexity and annotation coverage, a 3 is appropriate.

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 concise sentence that fronts the key information (action and resource) with no filler or unnecessary repetition. It earns its place completely.

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 simple read-only tool with one parameter and no output schema, the description provides enough to understand what to expect (a list of widgets for the given dashboard). Although it omits details about widget structure or response format, the context is sufficient for this tool's complexity, so a 4 is justified.

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 has 100% coverage for the single parameter 'dashboardId' with a clear description ('Dashboard ID to get widgets for'), so the schema carries the semantic load. The description only repeats the concept of a specific dashboard without adding syntax, format, or additional context, warranting the baseline score for high schema coverage.

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 identifies the action ('Get the list of widgets') and the resource ('a specific Cloud Insight dashboard'), using a specific verb and scoping. It also implicitly distinguishes from siblings like ncloud_list_dashboards (lists dashboards, not widgets) and ncloud_get_dashboard_widget_image (gets widget image, not list).

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?

The description states what the tool does but provides no explicit guidance on when to use it versus alternatives, such as ncloud_query_widget_preview or ncloud_get_dashboard_widget_image. There is no mention of prerequisites, exclusions, or context that would help an agent choose this tool over a sibling.

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