ncloud_export_mongodb_backup

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

The description states 'Export MongoDB backup files to Object Storage,' which implies writing files to Object Storage—a side effect. However, annotations declare readOnlyHint: true, creating a direct contradiction. No additional behavioral traits such as asynchronous execution or permission requirements are disclosed.

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 directly conveys the tool's purpose with no extraneous content. It is efficiently front-loaded and easy to parse.

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?

The description is minimal and omits critical operational context, such as whether the export is asynchronous, how to monitor progress, required permissions, or what the API response contains. The contradiction between the description's implied side effect and readOnlyHint further complicates the agent's understanding of the tool's behavior.

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 description coverage is 100%, so parameters are fully documented in the schema. The description does not add extra meaning about parameters beyond what the schema already provides, which is the baseline for this dimension.

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 ('Export') and clearly identifies the resource ('MongoDB backup files') and destination ('Object Storage'). It distinguishes the tool from siblings like ncloud_export_mongodb_log and ncloud_export_mysql_backup by focusing on MongoDB backups.

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 provides no guidance on when to use this tool compared to alternatives. It does not mention prerequisites, exclusions, or why one might choose export over other MongoDB operations. There is no contextual information about when this operation is appropriate.

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