ncloud_gtm_get_policy_resources

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

The description states 'Get', consistent with the readOnlyHint annotation. No additional behavioral traits are disclosed beyond what annotations already indicate. 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, concise sentence that efficiently conveys the purpose without unnecessary words. It is appropriately front-loaded and easy 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's simplicity (one parameter, no output schema), the description is adequate but lacks any indication of the return value or structure of 'resource details'. More context would be helpful, especially among numerous sibling tools.

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?

Input schema has 100% coverage for its single parameter 'policyId', with description 'Policy ID'. The description does not add any extra meaning or context 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 clearly states it retrieves 'resource details for a specific Global Traffic Manager policy', clearly indicating the verb and resource. It distinguishes from siblings like 'ncloud_gtm_get_policy_detail' by specifying 'resource details', though it does not explicitly differentiate from all related tools.

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 guidance is provided on when to use this tool versus alternatives (e.g., ncloud_gtm_list_policies, ncloud_gtm_get_policy_detail). There is no mention of appropriate contexts or when not to use this tool.

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