ncloud_gtm_update_policy_resources

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 'all resources' scope, implying a wholesale replacement of the resource set, which is meaningful beyond the annotations. However, it does not explicitly state that existing resources are overwritten or that the provided resourceGroups array becomes the complete new configuration.

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 of nine words. Every word earns its place, and there is no redundant or boilerplate content.

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 moderately complex update tool with no output schema, the description covers the basic purpose but lacks usage guidance and explicit replacement/overwrite semantics. The schema compensates for parameter details, but the absence of any reference to related tools or operational context leaves gaps.

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 description coverage is 100%, with both policyId and resourceGroups described in the input schema. The description adds little beyond the schema, though 'all resources' hints that resourceGroups represents the full desired set. Baseline 3 is appropriate since the schema already does the heavy lifting.

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 states a specific verb and resource: 'Update all resources for a specific Global Traffic Manager policy.' The qualifier 'all resources' clearly distinguishes this from the sibling tool ncloud_gtm_update_policy_resource (singular), making the scope unambiguous.

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 such as ncloud_gtm_update_policy_resource (singular) or ncloud_gtm_get_policy_resources. There are no exclusions, prerequisites, or context about whether this is a full replacement operation vs. a targeted update.

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