ncloud_get_fabric_cluster_pools

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

Annotations already set readOnlyHint=true, so the description adds minimal behavioral context by specifying 'available' and 'physical resource pools'. It does not disclose pagination, rate limits, or what happens if no pools exist.

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, concise sentence of 9 words. It is front-loaded with the core action, but lacks structured details like parameter usage or output hints.

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 list tool with one optional parameter and no output schema, the description is adequate but minimal. It does not explain default behavior (e.g., lists all pools if no filter) or return format.

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 input schema covers 100% of parameters, with the parameter description already explaining filtering by pool numbers. The tool description adds no extra meaning beyond what the schema provides.

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 it lists fabric cluster pools and clarifies they are physical resource pools. Among siblings, ncloud_list_fabric_clusters lists clusters, so the tool is differentiated by resource type. However, it does not explicitly mention the sibling tool for disambiguation.

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 is provided on when to use this tool versus alternatives (e.g., ncloud_list_fabric_clusters for clusters) or when not to use it. Context on prerequisites or filtering behavior is absent.

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