ncloud_get_subnet_detail

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

The annotation readOnlyHint=true already signals this is a safe read operation. The description 'Get detailed information' is consistent with that and adds no additional behavioral context such as return format, pagination, required permissions, or rate limits. With the annotation covering safety, the description adds only slight value by clarifying it targets a specific resource rather than a broad query.

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, direct sentence that conveys the essential purpose without any extraneous words. Every word earns its place, and it's front-loaded with the verb 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?

For a simple, single-parameter, read-only tool with no output schema, the description is nearly complete. It clearly states what the tool does. However, it doesn't hint at what kind of 'detailed information' is included (e.g., VPC, network ACL, status), though such details are often implied by domain knowledge. A minor gap, but acceptable for this simplicity level.

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 description coverage is 100%: the only parameter subnetNo is described as 'Subnet number to query' in the schema itself. The tool description repeats no further parameter details, so it adds no meaning beyond the schema. Baseline 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 'Get detailed information about a specific subnet' uses a specific verb ('Get') and a clear resource ('subnet'), and it distinguishes itself from the sibling tool ncloud_list_subnets by targeting a single subnet rather than listing all. The scope is unambiguous.

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 when to use the tool (when you need details about one specific subnet), but it does not explicitly mention alternatives or exclusions. For example, it doesn't state 'Use ncloud_list_subnets to find subnet numbers' or contrast with list operations. Guidance is minimal beyond the name and purpose.

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