ncloud_ses_add_node

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

Annotations declare destructiveHint: false, but the description fails to disclose important behavioral traits such as potential downtime, cost implications, asynchronous nature, or effect on cluster operations. Basic transparency is missing.

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 a single, concise sentence with no wasted words. However, it could be slightly expanded to include essential usage hints without losing conciseness.

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?

For a mutation tool that modifies cluster capacity, the description is too sparse. It lacks information about return values, confirmation of success, any required cluster state, or relationship to linked tools like ncloud_ses_get_cluster_detail.

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?

With 100% schema coverage, the schema already defines the parameters adequately. The description does not add additional semantic meaning beyond the schema's property descriptions, so baseline score of 3 applies.

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 the action (Add), resource (data nodes), and context (Search Engine Service cluster). It distinguishes this tool from sibling SES tools like ncloud_ses_change_node_spec or ncloud_ses_delete_cluster.

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 or why to use this tool, such as scaling scenarios, prerequisites (e.g., cluster state), or when to consider alternatives like ncloud_ses_change_node_spec or ncloud_ses_create_cluster.

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