ncloud_resource_list_resources

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

ReadOnlyHint annotation already signals safety. Description adds conditional behavior (NRN triggers detail), but omits pagination behavior, response format, or any constraints. Meets minimum but adds little beyond annotation.

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, front-loaded with action and resource. No wasted words. Efficiently communicates core purpose and key conditional behavior.

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?

With 10 parameters and no output schema, description should elaborate on pagination defaults (page/size), sorting, or what the returned list contains. Currently under-specified for a complex listing tool.

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 covers 100% of parameters. Description adds mention of NRN and 'tags and groups', but the latter is ambiguous and adds minimal value beyond schema descriptions. Meets baseline for high coverage.

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 verb 'List', resource 'resources managed in Ncloud', and distinguishes between list and detail when NRN is provided. This effectively differentiates from sibling tools that list specific resource types.

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?

Implies usage for general resource listing, but does not explicitly state when to use this tool versus alternatives like ncloud_list_servers or ncloud_list_vpcs. Lacks when-not-to-use guidance.

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