ncloud_search_logs

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

The description only restates the action 'search' which is consistent with the readOnlyHint annotation, but adds no extra behavioral context such as search scope, default time windows, or pagination behavior. The annotation already covers safety, so the description contributes little beyond the tool name.

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 with no filler or redundant information. It is appropriately front-loaded, offering the core purpose immediately, though it could benefit from a few more details without becoming verbose.

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?

With 8 parameters, no output schema, and minimal description, the tool is under-documented. The description does not explain return values, pagination results, or any limitations on what logs can be searched, leaving the agent without essential information to correctly invoke and interpret the tool.

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?

Input schema coverage is 100%, with every parameter having a description including defaults (pageNo, pageSize), examples (interval '5m/1h/1d'), and allowed values (regionCode 'kr, krs'). The description itself adds no parameter detail, but the schema fully documents the parameters, so baseline 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 clearly states the action ('Search') and the resource ('collected logs in Cloud Log Analytics'). It distinguishes this from many sibling tools by focusing on searching logs rather than exporting, counting, or listing them, though it doesn't explicitly name alternatives.

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 like ncloud_export_logs, ncloud_get_log_count_total, or ncloud_search_events. Given the large set of related log and event tools, this lack of direction leaves the agent to guess which tool fits the task.

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