ncloud_sourcedeploy_create_project

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

The annotations already indicate destructiveHint=false, which is consistent with creation. The description adds the dryRun preview behavior, but does not disclose other traits like whether the project is immediately usable or any naming conflict behavior. Given the annotation coverage, the description adds minimal extra 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 two short sentences with the main action front-loaded. No unnecessary words or repetition. Every sentence earns its place.

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?

The tool is simple with only two parameters and no output schema, so the description is adequate for basic use. However, it could mention prerequisites (e.g., region context) or what data the preview returns, making it slightly incomplete.

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 description coverage is 100% for both parameters. The description only restates the dryRun parameter from the schema, adding no new semantic meaning. Baseline 3 is appropriate since the schema already documents the parameters adequately.

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 'Create a new SourceDeploy deployment project,' using a specific verb and resource name. It distinguishes this tool from siblings like ncloud_sourcedeploy_list_projects and ncloud_sourcedeploy_delete_project, which have different purposes.

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 using dryRun=true to preview without creating, which provides basic usage guidance. However, it lacks explicit when-to-use or when-not-to-use instructions compared to alternatives, such as when an update operation would be more appropriate.

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