ncloud_gtm_update_policy_resources

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

Annotations declare idempotentHint=true and destructiveHint=false, which the description does not contradict. However, the description adds no behavioral context beyond the annotations, such as whether the tool overwrites all existing resources or requires the policy to be in a specific state.

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 that efficiently conveys the core purpose. It is concise and front-loaded, though it could benefit from slightly more detail.

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 lacks information about return values or side effects, especially important given the complex nested parameter schema and no output schema. It is minimally adequate for a straightforward update operation.

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 descriptions for both parameters. The description does not add any meaning beyond what the schema already provides. The tool name implies that resourceGroups is the full set, but no further clarification is given.

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 verb 'Update' and resource 'all resources for a specific Global Traffic Manager policy'. It distinguishes from sibling tools like 'ncloud_gtm_update_policy_resource' which updates a single resource, and 'ncloud_gtm_get_policy_resources' which retrieves resources.

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 provides no guidance on when to use this tool over alternatives (e.g., 'ncloud_gtm_update_policy_resource' for single resource updates). No prerequisites, conditions, or exclusion criteria are mentioned.

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