ncloud_cdss_get_broker_info

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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds that it retrieves endpoints and ports, which is useful but minimal. No additional behavioral traits (e.g., permissions, limits) are disclosed.

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, clear sentence with no wasted words. It is front-loaded and concise.

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, read-only tool with a single parameter and no nested objects or output schema, the description is adequate. It specifies the resource and what info is retrieved, but could be more complete (e.g., mention of return format or that it's for CDSS only which is already implied).

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 description coverage is 100% for the single parameter (serviceGroupInstanceNo), which already describes it as 'Cluster instance number'. The description's mention of 'CDSS cluster' adds little extra meaning beyond the schema.

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 uses a specific verb 'Get' and clearly identifies the resource: broker node communication info (endpoints, ports) for a CDSS cluster. This distinguishes it from sibling tools like ncloud_cdss_get_cluster_detail or ncloud_cdss_get_cluster_status.

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 guidance on when to use this tool versus alternatives (e.g., get_cluster_detail) or prerequisites. It does not mention that the tool is read-only (though annotation covers this) or any context needed.

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