ncloud_gtm_get_profile_detail

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

The annotation readOnlyHint=true already communicates that this is a safe read operation, and the description's 'Get detailed information' is consistent with that. However, the description adds no additional behavioral context such as required permissions, pagination, error conditions, or what details are returned. It provides no value 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, front-loaded sentence with no unnecessary words. It efficiently conveys the tool's function without repetition or fluff. Every word contributes to understanding the tool's purpose.

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 tool with only one parameter, a read-only annotation, and no output schema, the description provides enough information to know what the tool does and which resource it targets. It does not describe the return format, which is a minor gap, but overall it is reasonably complete for its simplicity.

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 only parameter domainId is fully described in the schema with 100% coverage, so the schema carries the meaning. The description does not add any additional elaboration about the parameter, such as how to obtain it or any constraints. Baseline 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 uses the specific verb 'Get detailed information' and identifies the resource as 'specific Global Traffic Manager profile (domain)', clearly distinguishing it from list operations and policy tools. The word 'specific' indicates this is for a single entity, and the parenthetical '(domain)' disambiguates the resource type from other GTM elements.

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 makes it clear that this tool is for retrieving details of a specific profile, which gives an implied use case. However, it does not explicitly state alternatives, exclusions, or prerequisites like obtaining the domainId from a list call. The context is clear enough for a simple tool, but lacks explicit when-not-to-use guidance.

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