ncloud_gtm_get_policy_detail

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

The annotation already declares readOnlyHint=true, which the description aligns with by stating it 'get's information. However, the description does not add additional behavioral context such as what constitutes 'detailed information', any rate limits, or response structure. With annotation, the bar is lower, but minimal value is added.

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 sentence with no redundant information. It is appropriately sized and front-loaded, earning a high score for conciseness.

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?

The description is vague about what 'detailed information' includes, and there is no output schema to clarify return values. While the tool is simple with one parameter, a user would benefit from knowing the types of data returned. Scores average for this dimension.

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 coverage is 100% for the single parameter (policyId) with a basic description 'Policy ID to query'. The description does not provide extra semantic meaning beyond the schema, so baseline score of 3 is appropriate.

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 specifies the verb 'Get' and the resource 'detailed information about a specific Global Traffic Manager policy'. It correctly indicates that the tool retrieves details for a single policy, but does not differentiate from sibling tools like ncloud_gtm_list_policies or ncloud_gtm_get_profile_detail.

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?

No usage guidelines are provided. The description does not explain when to use this tool over alternatives such as listing policies or getting profile details, nor does it mention any prerequisites or context.

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