ncloud_cdss_get_config_group_detail

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

The readOnlyHint annotation already indicates a safe read operation, so the description does not need to cover safety. It adds minimal behavioral context by mentioning 'including Kafka settings', which hints at response contents, but does not disclose potential nuances like pagination, errors, or required prerequisites. The description does not contradict 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?

The description is a single, front-loaded sentence with no redundant words. It efficiently communicates the tool's purpose and key scope.

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?

While the tool is relatively simple with one parameter and a read-only annotation, the description omits guidance on the response structure beyond 'details including Kafka settings'. With no output schema, the description should ideally clarify what fields or information are returned. The description is adequate but not comprehensive.

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% since configGroupNo is described as 'Config group number'. The description does not add further meaning, such as format or where to obtain the value, but the baseline of 3 is appropriate given full schema coverage.

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 tool gets Config Group details, using the specific verb 'Get' and identifying the resource. The addition of 'including Kafka settings' distinguishes it from the sibling tool ncloud_cdss_get_kafka_config, which focuses specifically on Kafka configuration.

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 implies usage for retrieving details of a specific config group, but it does not explicitly state when to choose this over alternatives like ncloud_cdss_list_config_groups or ncloud_cdss_get_kafka_config. No when-not or alternative tool references are provided, though the context suggests it's for full config group details.

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