ncloud_pipeline_list_sourcedeploy_projects

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

The readOnlyHint annotation already declares the safe read-only nature, and the description correctly aligns with that. The description adds little behavioral depth beyond stating the listing action; it does not disclose pagination, return format, or any account-specific restrictions. With annotations present, a baseline 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, front-loaded sentence that directly communicates the action and purpose with no unnecessary words. It is concise and to the point.

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 tool with complete schema documentation and read-only annotations, the description is adequate. It indicates the general purpose and relies on the schema for parameter details. It does not describe the response structure, but that is not critical for a list operation. Slightly more detail on return values or criteria would have earned a 5.

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?

The input schema has 100% description coverage for all three parameters (pageNo, pageSize, searchWord), so the schema already fully explains parameter semantics. The description does not add extra meaning to the parameters, making the baseline 3 the correct score.

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 a list operation on SourceDeploy projects with the specific purpose of pipeline task configuration. It uses a specific verb ('List') and resource ('SourceDeploy projects'), and the qualifier 'for pipeline task configuration' distinguishes it from the generic ncloud_sourcedeploy_list_projects sibling.

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 gives clear context by indicating this is for pipeline task configuration, which implies the tool should be used when selecting a SourceDeploy project within a pipeline. However, it does not explicitly call out alternatives or exclusions, so it falls short of a 5.

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