ncloud_serverless_export_logs

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

The description describes a POST export operation that writes logs to Object Storage and returns a 202 Operation, which implies a side-effecting, non-read-only action. This directly contradicts the annotations declaring readOnlyHint=true. The async status detail is useful, but the contradiction is disqualifying.

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 one compact sentence that front-loads the action and scope, then adds the endpoint, expected response code, and prerequisite. Every element earns its place and no filler is present.

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 conveys the core action and async nature via '202 Operation', but with no output schema it does not explain what the operation returns or how to track its progress. The annotation contradiction also undermines the overall operational context, leaving the definition incomplete.

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%, and the schema already describes all parameters including logs, bucketName, uploadPath, clusterName, and instanceName. The description adds little beyond restating the 1-10 count and destination, so it does not meaningfully improve on the schema.

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 a specific verb ('Export'), the resource ('log files of an instance'), the destination ('Object Storage'), and even the count range (1-10). It also identifies the endpoint and success response, making the tool's purpose unambiguous and distinct from related log-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 gives a clear usage context: exporting 1-10 instance log files to Object Storage, and a key precondition ('Requires an Object Storage subscription'). It does not explicitly name alternative tools such as ncloud_serverless_list_logs or ncloud_get_log_export_history, so it stops short of full when/when-not guidance.

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