ncloud_gtm_get_policy_detail

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

The description only states it retrieves info, which aligns with the readOnlyHint=true annotation but adds no behavioral context (e.g., error behavior, return structure, or required permissions). 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?

A single concise sentence with no redundancy. It is appropriately front-loaded and contains exactly the necessary information.

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 simple single-parameter read operation, the description is functional but omits what 'detailed information' includes. With no output schema, a bit more specificity about the returned policy details would improve completeness.

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% with policyId described as 'Policy ID to query'. The description does not add any parameter semantics, so the baseline of 3 applies.

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 Global Traffic Manager policy, using a specific verb and resource. It distinguishes from list tools but doesn't explicitly contrast with the sibling get_policy_resources tool.

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 like ncloud_gtm_list_policies or ncloud_gtm_get_policy_resources. The word 'specific' implies an existing policy ID, but prerequisites or alternative scenarios are not mentioned.

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