ncloud_export_logs

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

The description states logs are exported 'to an Object Storage bucket', which creates new objects and therefore mutates the environment, yet annotations declare readOnlyHint=true. This is a direct contradiction of the declared safety profile, and the description adds no other behavioral context (overwrite behavior, permissions, output naming).

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?

A single efficient sentence with no filler, and the action-to-destination mapping is front-loaded. It is appropriately sized, though it is arguably too terse given the operation's complexity.

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 covers the essential what and where, and the schema fully documents parameters, with no output schema to explain. However, for an export operation it omits prerequisite steps, destination/overwrite semantics, and any hint of async or history behavior that ncloud_get_log_export_history implies, leaving meaningful gaps.

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 all seven parameters (keyword, logTypes, regionCode, timestamps, bucketname, regionNo) are already documented in the schema. The description adds no filter syntax, timestamp format, or bucket-location detail beyond that, so the baseline 3 applies.

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 names a specific verb ('Export'), a specific resource ('searched logs'), and a destination ('Object Storage bucket in Cloud Log Analytics'). An agent can distinguish it from siblings like ncloud_search_logs or ncloud_get_log_export_history, though no sibling is named explicitly.

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?

There is no statement of when to use this tool versus alternatives, no mention that a prior search is required (the phrase 'searched logs' only hints at it), and no reference to related tools such as ncloud_search_logs or ncloud_list_export_buckets. The agent must infer the workflow entirely.

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