ncloud_cdss_disable_public_endpoint

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

The description adds no behavioral context beyond what annotations already provide (idempotentHint=true, destructiveHint=false). It does not describe side effects, dependencies, or what happens to existing connections when the public endpoint is disabled.

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, front-loaded sentence with no superfluous words. It efficiently conveys the core function.

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 tool, the description is moderately complete. It states the action and target, but lacks context about reversibility, prerequisite cluster state, or confirmation that the operation is idempotent (though annotations cover that). Given the tool's simplicity, it is functional but not enriched.

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 description does not add meaning beyond the input schema, which already has 100% coverage for the single parameter 'serviceGroupInstanceNo'. The schema's description 'Cluster instance number' is present, and the tool description provides no additional parameter guidance.

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 public endpoint for broker nodes' clearly states the action (disable) and the specific resource (public endpoint for broker nodes). It distinguishes the tool from siblings like 'enable_public_endpoint' and 'disable_public_domain' by specifying the exact resource type.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or scenarios where this tool is appropriate or contraindicated.

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