ncloud_assign_secondary_ips

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

With no annotations, the description should fully disclose behavior. It mentions input choices but does not explain whether assignment is additive or replaces existing IPs, potential side effects, or limits on count.

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 conveys the core functionality without any unnecessary words. It is front-loaded and efficient.

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 mutation tool without an output schema, the description should mention the expected result (e.g., list of assigned IPs) or confirmation. This is missing, but the description is adequate for a simple 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?

The schema already describes the parameters with 100% coverage. The description adds value by clarifying 'specific IPs' and 'auto-assign count', though more details (e.g., IP format, count range) would be better.

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 action 'Assign secondary IPs' and the resource 'network interface'. It implies two methods (specific IPs or count), distinguishing it from the sibling 'ncloud_unassign_secondary_ips'.

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 implies a mutual exclusivity between 'secondaryIpList' and 'secondaryIpCount' but does not explicitly state when to use each, nor does it provide context on prerequisites or alternatives like unassigning IPs.

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