ncloud_sourcedeploy_create_project

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

The annotation only indicates destructiveHint=false, which is consistent with a creation tool. The description adds the dryRun preview behavior, which is helpful, but it doesn't disclose other behavioral aspects such as potential side effects (e.g., resource creation costs, name uniqueness conflicts, or required permissions). For a mutating create operation, more transparency about consequences would be beneficial, but the dryRun note provides some safety 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?

The description is exceptionally concise: one sentence for the core purpose and a second sentence for the dryRun tip. Every word earns its place, with no fluff or redundant details. It is front-loaded with the primary action.

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 (2 parameters, no output schema, no nested objects), the description provides sufficient context: it names the resource, states the creation action, and explains the preview capability. It doesn't cover every possible scenario (e.g., permissions prerequisites), but for a straightforward create operation, it is adequately complete. The schema fills in parameter details.

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 already covers both parameters completely (100% coverage): 'name' includes format constraints and 'dryRun' is described as returning a preview without actually creating. The description's mention of dryRun=true adds no new semantics beyond what the schema already states, so it meets the baseline but does not elevate it.

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 states a specific action: 'Create a new SourceDeploy deployment project.' This clearly distinguishes it from sibling tools such as ncloud_sourcedeploy_delete_project, ncloud_sourcedeploy_list_projects, and ncloud_sourcedeploy_create_stage, making the tool's purpose unambiguous.

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 a clear usage context for the tool: creating a SourceDeploy project. It also includes a practical guideline for a key alternative mode: 'Use dryRun=true to preview without creating.' While it doesn't explicitly mention alternatives like listing or deleting projects, the primary usage and the dryRun option are well communicated.

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