ncloud_set_lb_subnet

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

Annotations already provide idempotentHint=true and destructiveHint=false, so the description doesn't need to repeat those. However, it adds no further behavioral context (e.g., effect on existing traffic, whether subnets are replaced or merged). Description 'Set subnets' is consistent but not enriching.

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?

Description is a single sentence, short and front-loaded. All words are meaningful. However, it may be too concise, omitting important details like the effect on existing subnets.

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?

Despite full schema coverage, the description is minimal and does not explain the broader context of the operation (e.g., does it replace all subnets or add? Is there a return value? Are there constraints?). For a mutation tool, this is incomplete.

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 clear parameter descriptions. The tool description adds no additional meaning beyond what the schema already provides. A baseline score of 3 is appropriate since schema 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?

Description clearly states the verb-resource pair 'set subnets' on a load balancer instance. Among siblings, there are many load balancer tools (create, delete, change config, etc.), but this one is specific to subnet assignment, which helps differentiate. However, it doesn't explicitly distinguish from similar sibling like ncloud_nks_update_lb_subnet.

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 on when to use this tool, prerequisites, or alternatives. Does not mention if the load balancer must be in a certain state or if subnets are replaced or appended. Lacks context for an agent to decide when to invoke this vs. other load balancer tools.

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