ncloud_export_logs

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

The description says 'Export searched logs' which implies a write operation to Object Storage, but the annotations declare readOnlyHint=true. This is a direct contradiction. Additionally, the description fails to disclose important behavior such as whether the export is asynchronous, overwrites existing objects, or requires specific permissions.

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 is easy to parse. It is appropriately short but lacks any structural elements like examples or context blocks, making it functional but not exemplary.

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?

Given that this tool has 7 parameters, no output schema, and performs a side-effecting export, the description is incomplete. It doesn't explain how search criteria are supplied, what the timestamps should look like, or what the result of the export is. It also doesn't reference related tools for export history or bucket listing, leaving significant 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%, and each parameter already has a basic description. The tool description adds no additional semantic meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 ('Export searched logs') and a destination ('Object Storage bucket'), which clearly identifies the tool's purpose. However, 'searched logs' is somewhat ambiguous and doesn't fully distinguish it from related log tools like ncloud_search_logs or ncloud_get_log_export_history.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention that it works with the search parameters described in the schema or how it relates to ncloud_search_logs and ncloud_list_export_buckets, leaving the agent without clear direction.

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