ncloud_serverless_create_imported_backup

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

With only destructiveHint=false in annotations, the description carries most of the behavioral burden. It discloses that the call is asynchronous (202 Operation), supports up to 16 TiB, and offers a dryRun preview mode—useful behavioral context beyond what the annotations provide.

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?

Two tight sentences: the first front-loads the core action, endpoint, async behavior, and size limit; the second adds the restore workflow and dryRun preview. Every sentence earns its place with no filler.

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 an async create operation with no output schema, the description covers what it does, the endpoint, the size cap, the downstream restore step, and the preview mode. It doesn't describe response shape or polling, but the 202 status and sibling operation tools mitigate that gap.

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 the baseline of 3 applies. The description reiterates dryRun=true for previewing, but this largely duplicates the schema's own parameter description and adds no significant new semantics for bucketName, objectPath, or engineVersion.

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 states a specific action (import a backup file from Object Storage as an imported backup), names the resource, and includes the API endpoint. The follow-up reference to ncloud_serverless_restore_cluster clearly differentiates this import operation from related serverless backup tools such as export, list, get, and delete imported 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?

It provides concrete workflow guidance: after importing, restore using ncloud_serverless_restore_cluster with source.type=IMPORTED_BACKUP, and use dryRun=true to preview. This tells the agent when this tool fits into the backup/restore flow, though it doesn't explicitly enumerate when not to use it versus alternatives.

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