ncloud_list_mongodb_logs

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

Annotations already declare readOnlyHint=true, and the description adds no behavioral context such as log types, filtering options, pagination, or response content. It merely restates the tool's action, so it provides minimal value beyond the structured annotation.

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 concise sentence that immediately states the action and resource. No extraneous words, and appropriately sized for this simple tool.

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 read-only list operation with one fully-specified parameter, the description is minimally adequate for tool selection. However, it does not disclose what log data is returned, whether pagination applies, or how it differs from the export_mongodb_log tool, leaving gaps for an agent expecting complete context.

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?

The single parameter cloudMongoDbServerInstanceNo is fully described in the schema ('Cloud MongoDB server instance number'), and the description adds no additional semantics or usage details, consistent with the 100% schema coverage baseline 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 uses a specific verb ('List') and resource ('server logs for a Cloud DB for MongoDB server instance'), clearly distinguishing this from sibling tools like ncloud_list_mongodb_instances or ncloud_list_mongodb_backups. The scope is unambiguous.

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 explicit guidance is provided about when to use this tool versus alternatives, such as ncloud_export_mongodb_log for exporting logs or ncloud_list_mysql_logs for MySQL. The intended use case is implied by the verb and resource, but exclusions/alternatives are absent.

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