ncloud_list_init_scripts

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

Annotations already provide readOnlyHint=true, so the description's job is to add behavioral context beyond that. It adds only the regional scope ('current region') but does not mention pagination behavior, potential size limits, or return format. This is minimal added value.

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 sentence of 7 words, no fluff, and directly communicates the tool's purpose. Every word is earned, making it highly efficient.

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?

With no output schema, the agent lacks information about return structure. The description does not explain what fields are returned, how pagination works, or how to interpret results. Given that sibling tools for related operations exist, more context would help the agent navigate the toolset effectively.

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% for all three parameters (pageNo, pageSize, initScriptNoList), so the description does not need to add parameter info. Baseline score of 3 is appropriate as the description adds no extra semantic meaning 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 verb 'List' and the resource 'init scripts' with a scope 'in the current region'. It distinguishes itself from sibling tools like ncloud_get_init_script_detail (which retrieves a single script), ncloud_create_init_script, and ncloud_delete_init_scripts, making its purpose 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 does not explicitly state when to use this tool versus alternatives like ncloud_get_init_script_detail or when pagination is needed. It implies listing all scripts but lacks guidance on filtering or context for choosing this tool over others.

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