ncloud_resource_list_resources

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that NRN returns a single resource detail with tags and groups, which is useful behavioral context. However, it does not disclose pagination, filtering semantics, or response structure.

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?

Two sentences, concise and front-loaded with the primary action. There is no wasted wording, and the NRN conditional is integrated efficiently.

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?

The description is adequate for a simple list tool with a detailed schema, but lacks output format, pagination information, or how filters combine. The NRN case is covered, but the general list behavior is under-specified.

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?

All 10 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds only the NRN behavior with tags/groups, which is a minor addition beyond the schema. No significant semantic enrichment for other parameters.

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 tool lists resources managed in Ncloud, using a specific verb and resource. It also explains the NRN special case, but does not explicitly differentiate from other specific list tools such as ncloud_list_servers.

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 provides conditional usage guidance for when NRN is specified, but offers no alternatives or when-not-to-use guidance. It implies general resource listing but does not mention when to prefer this over sibling list tools.

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