ncloud_list_integrations

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

The readOnlyHint annotation already declares this is a safe read operation. The description adds the paging behavior (though that is also reflected in the pageNum/pageSize parameters) and clarifies it returns a list. It does not contradict annotations and provides minimal additional context beyond what annotations and schema 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?

The description is a single, focused sentence that immediately states the action and resource. It avoids redundant phrasing and every word contributes meaning. It is optimally concise for a simple list operation.

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 list tool with no required parameters and no output schema, the description adequately conveys what the tool returns (a list of integrations) and that it is paged. It does not explain the return structure in detail, but for this low-complexity tool, the description plus schema is sufficient for an agent to invoke it correctly.

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 documents all three parameters (query, pageNum, pageSize) with descriptions and defaults, giving 100% coverage. The description adds no extra parameter semantics, so the baseline of 3 is appropriate since the schema carries the full burden.

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 verb 'Get the list' and the specific resource 'Cloud Insight integrations', and notes it is paged. This distinguishes it from sibling tools like ncloud_get_integration (singular) and the create/update/delete operations. The purpose is unambiguous.

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 implies this is the tool for listing integrations, but it does not explicitly state when to use it versus alternatives like ncloud_get_integration for a single integration. There is no explicit when-not-to-use or mention of alternative tools, so the guidance is only implied.

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