ncloud_create_sub_account

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

Annotations already mark destructiveHint=false. The description adds the dry run behavior, which is useful. However, it does not disclose other behavioral traits like side effects, idempotency, or permissions required. The added value beyond annotations is moderate.

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 sentences and one line, very concise. It is front-loaded with the action and includes a key feature. No wasted words.

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 high schema coverage, the description lacks context about what a sub account is, prerequisites, or the overall creation process. For a tool with 11 parameters and no output schema, the description is too brief to be fully informative.

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 the input schema already documents all parameters. The description does not add extra meaning beyond what is in the schema, except mentioning dryRun in context. 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 clearly states 'Create a new sub account (IAM user)', which is a specific verb and resource. It also mentions the dry run feature, adding specificity. This distinguishes it from sibling tools like ncloud_delete_sub_account.

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 is a usage hint. However, it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. The context is clear but lacking exclusions or alternative recommendations.

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