ncloud_search_logs

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds no further behavioral traits such as pagination limits, data volume considerations, or rate limits. Without annotations, this would be a 1, but with annotations present, the description adds minimal value beyond what is already indicated.

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 without any fluff or redundant information. It effectively communicates the core purpose in a front-loaded manner, earning a top score for efficiency.

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?

Despite having 8 parameters and no output schema, the description is extremely brief. It does not explain the nature of the logs, the return format, default behaviors (e.g., time range defaults), or any important constraints beyond what the schema provides. A richer description is needed for a tool with this level of complexity.

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?

The input schema provides 100% coverage with detailed descriptions for all 8 parameters. The description does not add any additional meaning beyond the schema, so the baseline score of 3 is appropriate. No parameter information appears solely in the description.

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 'Search collected logs in Cloud Log Analytics' uses a specific verb ('Search') and resource ('collected logs in Cloud Log Analytics'), clearly distinguishing it from sibling tools like ncloud_search_events (events) and ncloud_query_monitoring_data (monitoring data).

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 provides no guidance on when to use this tool versus alternatives such as ncloud_search_events or ncloud_query_monitoring_data. It lacks explicit when-to-use, when-not-to-use, or alternative recommendations, leaving the agent without context for selection.

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