ncloud_hadoop_list_notebook_buckets

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

Annotations already declare readOnlyHint=true, so the description is not needed for that. It adds the 'for Cloud Hadoop notebooks' scope, but lacks details on pagination, permissions, or error handling. Adequate but not rich.

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?

Single sentence with 7 words, no redundancy. Front-loaded with action and resource. Efficient.

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?

Lacks output description. For a list tool with no output schema, a note on what is returned (e.g., bucket names, metadata) would improve completeness. Otherwise adequate.

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 descriptions for both parameters (regionCode and cloudHadoopInstanceNo). The description does not add meaning beyond what the schema already provides, so baseline 3 applies.

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 specifies 'List Object Storage buckets available for Cloud Hadoop notebooks', clearly identifying the action (list), resource (buckets), and context (Cloud Hadoop notebooks). It distinguishes from sibling tools like 'ncloud_hadoop_list_buckets' which likely targets general Hadoop buckets.

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 on when to use this tool versus alternatives such as 'ncloud_hadoop_list_buckets' or sibling bucket-listing tools. No prerequisites or context for selection provided.

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