ncloud_list_integrations

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

The description adds 'paged' beyond the readOnlyHint annotation, but does not detail pagination behavior, result limits, or other operational characteristics. Annotations already declare readOnlyHint=true, so the description provides marginal added transparency.

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, clear sentence with no unnecessary words. It is well-structured and front-loaded with the essential action.

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 paged list tool with no output schema, the description adequately conveys the purpose and paging. It does not describe return format, but parameters are well-documented in the schema. The tool is fairly complete given its simplicity.

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 coverage is 100% with descriptions for all three parameters (query, pageNum, pageSize). The tool description adds the context of pagination but no further parameter details, so it meets the baseline without significant added value.

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 resource 'list of Cloud Insight integrations', and notes 'paged'. It distinguishes from sibling tools like ncloud_get_integration which retrieves a single integration.

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 on when to use this tool versus alternatives (e.g., ncloud_get_integration for a single integration, or other list tools). No prerequisites or exclusions are mentioned.

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