ncloud_cdnplus_list_instances

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: that filtering by instance number and pagination are supported. It does not contradict the annotation and adds clarity about the operation's optional parameters.

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, well-structured sentence that front-loads the primary action and then notes optional parameters. There is no redundancy or filler.

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 operation with three optional parameters, the description covers the essential purpose and parameters. While there is no output schema to explain return values, the verb 'List' implies a collection result, which is sufficient for this tool.

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 all three parameters (pageNo, pageSize, cdnInstanceNo) described. The description groups them into 'filtering by instance number' and 'pagination', which adds mild organizational value but does not provide additional details 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 the tool's action ('List CDN+ instances') with a specific verb and resource. It also mentions optional filtering and pagination, which precisely scopes the operation and helps distinguish it from other CDN-related tools like monitoring or purge tools.

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 usage context by indicating this is for listing CDN+ instances with optional pagination and filtering, but it does not explicitly state when to use it versus alternative tools (e.g., global CDN listing or monitoring). No exclusions or preferred use cases are provided.

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