ncloud_run_pipeline

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

Annotations are empty, so the description carries full burden. It only says 'Execute a SourcePipeline pipeline' without disclosing whether it is destructive, idempotent, requires permissions, or what side effects occur. This is insufficient for behavioral understanding.

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 only 4 words, which is very concise. It directly conveys the action and resource without unnecessary fluff. Suitable for a simple tool.

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?

Given the tool's simplicity (1 param, no output schema), the description is incomplete. It does not explain what happens upon execution, how to monitor progress, error conditions, or return values. For a tool that triggers a pipeline run, more context is needed.

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%, and the schema describes projectId as 'Pipeline ID to run'. The description adds no additional meaning to the parameter, so baseline score of 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?

The description 'Execute a SourcePipeline pipeline' clearly states the action (Execute) and the resource (SourcePipeline pipeline). It distinguishes from sibling tools like ncloud_create_pipeline or ncloud_delete_pipeline, which have different verbs. However, it does not clarify what execution entails, such as triggering a run.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that it should be used on an existing pipeline, nor does it differentiate from ncloud_cancel_pipeline or other execution-related tools. There is no context on prerequisites.

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