ncloud_pipeline_list_sourcebuild_projects

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

Annotations already provide readOnlyHint=true, so the description does not need to restate safety. The description adds little beyond the annotations: it implies listing but does not explain pagination behavior (handled by parameters) or return format. With annotations covering the safety profile, a score of 3 is appropriate.

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 that is concise and front-loaded. It contains no filler or redundant information. Every word serves a purpose.

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 listing tool with optional parameters and no output schema, the description is fairly complete. It correctly places the tool in the context of pipeline task configuration. However, it does not describe the response structure or any additional behavior like maximum results. Considering simplicity and annotation coverage, it is slightly above adequate.

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%: all three parameters (pageNo, pageSize, searchWord) have descriptions. The tool description does not add any extra meaning or clarification beyond the schema. Baseline is 3 given high coverage.

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 'List available SourceBuild projects for pipeline task configuration', specifying the action (list), resource (SourceBuild projects), and context (for pipeline task configuration). This distinguishes it from general ncloud_sourcebuild_list_projects and similar pipeline listing tools like ncloud_pipeline_list_sourcecommit_repos.

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 to use it (e.g., during pipeline stage configuration) or when not to use it (e.g., for general SourceBuild project listing, use ncloud_sourcebuild_list_projects instead). No exclusions or prerequisites are given.

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