ncloud_list_pipelines

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

Annotations indicate readOnlyHint=true, and the description states 'List', which is consistent. However, the description adds no behavioral context beyond the read-only nature, such as result limits, ordering, or what data is returned. It provides minimal additional transparency.

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 conveys the core functionality without any extraneous words. It is concise and front-loaded with the key action and resource.

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 read-only list tool with no output schema, the description is adequate but incomplete. It does not describe the return value structure (e.g., what fields are in each pipeline object), which would help the agent understand the response. The missing output schema could be compensated with more detail in the description.

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 each parameter described. The description adds high-level context ('optional pagination and name search') that reinforces the schema, but does not provide meaning beyond what the schema already offers. Baseline 3 is appropriate.

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?

Description clearly states it lists 'SourcePipeline pipelines' with optional pagination and name search. The verb 'list' and resource 'pipelines' are specific, and the mention of 'SourcePipeline' distinguishes it from other list tools like ncloud_list_servers. However, it does not explicitly differentiate from sibling list 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 mentions optional pagination and name search, implying how to use the parameters but does not provide guidance on when to use this tool versus alternatives like ncloud_get_pipeline. No explicit when-to-use or when-not-to-use information is given.

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