ncloud_cdss_enable_public_endpoint

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a behavioral constraint—the need for a load balancer—which is not in the annotations or schema. It doesn't contradict annotations and provides useful context beyond the structured fields.

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 with zero waste. The core purpose is front-loaded, and the prerequisite and cross-reference are placed right after. Every word 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?

For a simple tool with 2 parameters and no output schema, the description covers the action, the target (broker nodes), and the key prerequisite (load balancer). Annotations handle idempotency and non-destructiveness. Nothing critical is missing for an agent to invoke it correctly.

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% and both parameters have descriptions. The description adds value by telling the agent how to source loadBalancerInstanceNo (via ncloud_cdss_get_load_balancers), which is extra guidance beyond the schema's static description. serviceGroupInstanceNo is adequately described as 'Cluster instance number' in the schema, so no further clarification is needed.

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: 'Enable a public endpoint for broker nodes.' It uses a specific verb and resource, and the phrase 'broker nodes' distinguishes it from sibling tools like ncloud_cdss_enable_public_domain and ncloud_cdss_disable_public_endpoint.

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 gives a clear prerequisite: 'Requires a load balancer' and points to the exact sibling tool to list load balancers. This tells the agent when it can use the tool and how to obtain a required parameter. It doesn't explicitly contrast with disable_public_endpoint, but the verb and name make the opposite case obvious.

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