ncloud_attach_policy_to_sub_account

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows the operation is safe and repeatable. The description adds 'Assign IAM policies' which is consistent but does not disclose whether assignments are additive or overwrite previous ones. Minimal extra value beyond 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, efficient sentence with no extraneous information. It is front-loaded with the core action and resource.

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 important context: whether the sub account must exist, whether policyIdList refers to existing policies, whether the assignment is additive or replaces existing assignments, and what the expected outcome is. For a mutation operation, this is insufficient even with annotations providing basic safety traits.

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% (both parameters described with names and types). The description does not add any meaning beyond what the schema provides. Baseline of 3 is appropriate as the schema carries the burden, but no additional semantic enrichment.

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 'Assign IAM policies to a sub account' clearly states the action (assign) and the resource (policies to a sub account). It is specific and distinguishes from sibling tools like 'attach_policy_to_group' which target a different resource.

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 versus alternatives (e.g., attach_policy_to_group, detach_policy_from_sub_account). It lacks context about prerequisites or scenarios, leaving the agent without decision support.

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