ncloud_get_mssql_target_subnets

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

The readOnlyHint annotation already signals this is a safe read operation. The description adds no extra behavioral context beyond the purpose itself, such as filtering behavior, response format details, or constraints. It repeats the schema's scope without providing additional transparency.

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, clear sentence with no wasted words. It is appropriately front-loaded, stating the verb and resource immediately, and earns its place without redundancy.

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 simple listing tool with good annotations, the description is adequate but minimal. It explains what it lists but does not elaborate on the return format or any additional semantics (e.g., whether it returns only unused subnets). Since there is no output schema, a bit more detail would have been beneficial, but the core function is clear.

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 fully describes both parameters (cloudMssqlInstanceNo and regionCode), so the description does not need to add parameter details. It doesn't, and since schema coverage is 100%, the baseline of 3 is appropriate.

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 a specific action ('List') and resource ('subnets available for Cloud DB for MSSQL'), and adds the scope 'within a specific instance'. It effectively distinguishes this tool from general subnet listing tools and similar ones for other database types, though it doesn't explicitly name alternatives.

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 the use case (listing subnets for a particular MSSQL instance) but provides no explicit guidance on when to use it versus alternative tools, such as ncloud_get_mssql_target_vpcs or equivalent tools for other database engines. No exclusions or alternative recommendations are mentioned.

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