ncloud_get_target_group_detail

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

Annotations already declare readOnlyHint=true, so the read-only nature is established. The description adds 'Get detailed information' which aligns with that. However, it does not disclose any additional behavioral traits such as required authentication, rate limits, or what specific details are returned. The description minimally adds beyond the annotation.

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 concise sentence with no unnecessary words. It is front-loaded with the action and resource, making it efficient for an AI agent to parse.

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?

Given the tool has one simple parameter, no output schema, and is straightforward, the description is mostly sufficient. However, it does not hint at the structure of the returned information, which could be helpful for an agent. Despite this, the simplicity justifies a high score.

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 description coverage is 100% (targetGroupNo described as 'Target group number to query'). The description does not add any additional meaning or context for the parameter beyond what the schema already provides. Baseline score of 3 applies due to high 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 retrieves detailed information about a specific target group. The verb 'Get' and resource 'detailed information about a specific target group' are specific and unambiguous. It distinguishes itself from sibling tools like ncloud_list_target_groups (which lists all target groups) and ncloud_create_target_group (which creates one).

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. It does not mention that this should be used after listing target groups or that other tools exist for creation or deletion. No context on prerequisites or when it is appropriate to invoke this tool is provided.

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