ncloud_get_flow_log_config

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

The readOnlyHint annotation already declares this is a safe read operation. The description adds the behavioral nuance that it returns all configurations by default and filters when a network interface number is provided. This is helpful but minimal; no additional context about response format, pagination, or permissions is given. The description is consistent with the annotation, so no contradiction.

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 consists of two crisp sentences with no filler. It leads with the action ('Get'), specifies the resource ('FlowLog configuration list'), and immediately explains the optional behavior. Every word earns its place.

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?

For a simple read-only list tool with one optional parameter and no output schema, the description is complete enough. It covers the two possible behaviors (all vs. filtered) and implies the return type is a list. It does not enumerate fields of a FlowLog configuration, but for this straightforward operation that is acceptable.

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 already describes the single parameter (networkInterfaceNo) with 100% coverage. The description reiterates the filtering functionality but adds no new semantic detail beyond what the schema provides. Baseline 3 is appropriate since the schema handles the heavy lifting.

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+resource: 'Get FlowLog configuration list.' It further explains the exact behavior: returns all configurations or filters by network interface number. This unambiguously distinguishes it from the sibling enable/disable flow log 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 communicates when to use the tool: to retrieve flow log configurations, either in full or filtered. It does not explicitly mention alternatives or exclusions, but the read intent is clear from the context and the readOnlyHint annotation. There are no close sibling tools that do the same thing, so this is sufficient.

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