ncloud_hadoop_list_objects

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

The description adds no behavioral details beyond the readOnlyHint annotation. It does not mention required permissions, error scenarios, or any side effects, which would be helpful for a listing operation. The annotation already indicates non-destructive behavior, so the description provides minimal added value.

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 very concise at one sentence with no wasted words. It is front-loaded with the action. However, it could include more context without sacrificing conciseness; for example, hinting at the relationship between parameters.

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 tool has 4 parameters and no output schema, the description does not explain what the returned list looks like or how parameters interact. It fails to mention that cloudHadoopInstanceNo is required or that bucketName, regionCode, and directoryName are optional filters. This leaves the agent with incomplete information for correct invocation.

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?

Input schema coverage is 100%, so the schema already documents all four parameters. The description does not add any extra meaning or clarify dependencies like cloudHadoopInstanceNo being required. Baseline 3 is appropriate because the description does not enhance parameter understanding beyond the schema.

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 'objects in Object Storage bucket linked to Cloud Hadoop', making the tool's purpose unambiguous. It distinguishes from sibling tools like ncloud_hadoop_list_buckets and ncloud_hadoop_list_clusters by specifying the object listing context.

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 like ncloud_hadoop_list_buckets or ncloud_hadoop_list_clusters. The description does not specify prerequisites, such as needing a bucket or instance, nor does it give context for typical use cases.

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