ncloud_list_objects

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

The annotations already declare readOnlyHint=true, so the description adds no additional behavioral context. It does not disclose pagination behavior, rate limits, or error scenarios, which would be valuable for a listing operation.

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, terse sentence. It is concise and wastes no words, but it could be more informative without becoming verbose. It is appropriately front-loaded.

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?

Given the lack of an output schema and the complexity of object storage listing (pagination, filtering), the description is incomplete. It does not explain the nature of the returned list, how pagination works, or how to use the parameters effectively. The tool's behavior is not fully 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 5 parameters are fully described in the input schema (100% coverage). The description adds no extra meaning beyond the schema, so a baseline of 3 is appropriate. The schema already explains marker, prefix, maxKeys, delimiter, and bucketName.

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 objects in an Object Storage bucket, providing a specific verb and resource. However, it does not differentiate from the sibling tool ncloud_ncs_list_objects, which appears to serve a similar purpose for a different service.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like ncloud_ncs_list_objects, ncloud_hadoop_list_objects, or other object-related operations. The agent must infer context from the name and siblings.

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