ncloud_list_object_versions

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

Annotations already declare `readOnlyHint: true`, indicating a safe read operation. The description adds no additional behavioral context beyond listing object versions. Since annotations cover the safety profile, the description is adequate but adds minimal extra 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 sentence of 10 words, highly concise and front-loaded. Every word is meaningful, with no redundancy or unnecessary detail.

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 list tool with 6 parameters and no output schema, the description only states the purpose. It lacks information about pagination behavior, response structure, or that the bucket must be versioning-enabled. While the schema covers parameters, the tool's overall behavior is not fully described, making it adequate but incomplete.

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 coverage is 100%, with all 6 parameters described in the schema. The description does not add any extra meaning or examples for parameters like prefix, delimiter, or pagination markers, so it provides no value beyond what the schema already offers.

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 verb 'list' and the resource 'all versions of objects' with a specific constraint 'in a versioning-enabled Object Storage bucket'. This distinguishes it from sibling `ncloud_list_objects` which lists current objects, not versions.

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 implicitly requires the bucket to be versioning-enabled, but does not explicitly state when to use this tool versus alternatives (e.g., `list_objects` for current objects). It provides clear context but lacks exclusions or explicit alternative mentions.

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