ncloud_list_mongodb_buckets

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

Annotations already declare readOnlyHint=true, indicating safety. The description adds behavioral context by specifying the scope (only buckets available for MongoDB backup export), which goes beyond the annotation and clarifies the tool's purpose.

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, front-loaded with the key action and resource. Every word serves a purpose, making it highly efficient and concise.

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 simple list tool with one optional parameter, annotations, and no output schema, the description adequately explains its scope and purpose. No significant gaps are present, though explicit mention of return format or pagination (if any) could further enhance completeness.

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 the regionCode parameter described as 'Region code (e.g., KR, JPN, SGN)'. The description does not add further meaning to the parameter, warranting the baseline score of 3.

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 it lists Object Storage buckets available for Cloud DB for MongoDB backup export. The verb 'List' and specific resource 'buckets available for Cloud DB for MongoDB backup export' differentiate it from sibling tools like ncloud_list_mssql_buckets and general bucket listing tools.

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 implies usage for MongoDB backup export buckets but lacks explicit guidance on when to use this tool versus alternatives like ncloud_list_buckets or other database-specific bucket listers. No when-not or alternative references are provided.

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