ncloud_cdss_disable_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 the scope 'broker nodes' but does not disclose potential side effects, such as whether active connections are dropped or whether the endpoint can be re-enabled. No contradiction with annotations.

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?

A single, concise sentence with no redundant words. The action and target are front-loaded, making it easy to scan and understand.

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 one-parameter operation, the description covers the core action. However, it lacks context about when to use it, what 'broker nodes' refers to, or any prerequisites. With no output schema and minimal annotations, an agent might still be uncertain about the exact effect or scope.

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 schema fully describes the only parameter, serviceGroupInstanceNo, as 'Cluster instance number' (100% coverage). The description does not add any additional meaning or context for this parameter, so the 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 'Disable the public endpoint for broker nodes' clearly states the action (disable) and the resource (public endpoint for broker nodes). It differentiates from siblings like 'ncloud_cdss_enable_public_endpoint' and 'ncloud_cdss_disable_public_domain' by explicitly targeting the broker nodes' 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?

No guidance is provided on when to use this tool versus alternatives such as 'enable_public_endpoint' or 'disable_public_domain'. The description does not mention prerequisites, conditions, or contexts where this operation is appropriate.

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