ncloud_imageoptimizer_list_projects

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

The description confirms the read-only nature (consistent with readOnlyHint annotation) and adds the behavioral detail of pagination. It does not contradict annotations but adds only modest value beyond them.

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. It is appropriately brief for a simple listing tool, though it could slightly expand on the return format without being verbose.

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?

Lacking an output schema, the description should provide more context about the response (e.g., fields returned per project). It only mentions pagination, leaving agents uncertain about the data shape. This is a significant gap for a listing 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 coverage is 100% with descriptions for both parameters. The description mentions 'pagination', which reinforces the role of pageNo and pageSizeNo, but adds little new meaning since the schema already defines them. With high coverage, baseline is 3.

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 action ('List') and the resource ('Image Optimizer projects'), and mentions pagination. It distinguishes this tool from siblings like ncloud_imageoptimizer_create_project and ncloud_imageoptimizer_list_rules, but could be more specific about the scope (e.g., 'all' projects).

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest other tools for specific cases (e.g., retrieving a single project). Agents must infer usage from context.

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