ncloud_create_pipeline

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

Annotations only provide destructiveHint=false, which is consistent with 'Create'. The description adds 'SourcePipeline' specificity but does not disclose additional behavior like return values, prerequisites, or the effect of dryRun. Since annotations are minimal, the description carries some burden but provides little extra behavioral context.

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?

One short, front-loaded sentence that captures the tool's purpose without waste. No redundancy or unnecessary detail.

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?

Despite the complex nested schema and no output schema, the description is minimal. It explains what the tool does but lacks information about return format, prerequisites beyond schema, or side effects. Adequate for tool selection but not fully complete.

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%, so all parameters are described in the schema. The description only mentions 'tasks' and 'optional triggers', which adds no meaning beyond the schema. 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?

The description uses a specific verb ('Create') and resource ('SourcePipeline pipeline'), and mentions key components ('tasks', 'optional triggers'). It clearly distinguishes from sibling update/delete/list/run pipeline 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 verb 'Create' clearly indicates when to use this tool (for creating new pipelines). However, it does not explicitly mention alternatives or exclusions (e.g., 'use update_pipeline for existing pipelines'). Context is clear enough without explicit alternatives.

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