ncloud_serverless_get_log_config

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

Annotations already provide readOnlyHint=true, and the description aligns by saying 'Get'. It adds useful behavioral context beyond the annotation by specifying the supported log types (BIN|SLOW_QUERY|ERROR|GENERAL) and the rotation fields (rotationType DAILY|SIZE, fileCount, megaBytes), which is valuable since no output schema is present. No contradiction exists.

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 dense sentence that front-loads the action and follows with the endpoint and response structure. There is no filler or repetition, and the compact notation communicates the return shape efficiently.

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 read-only tool with one fully documented parameter and no output schema, the description is nearly complete: it documents the endpoint, log types, and response fields. It lacks a brief routing note against ncloud_serverless_get_config or update_log_config, but that is a minor gap given the simple parameter surface.

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 the single clusterName parameter is already well documented. The description only reuses {clusterName} as a path placeholder, adding no new semantic detail beyond the schema, so the 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?

States a specific action and resource: 'Get log rotation settings per log type' with the endpoint and the exact config fields returned. The wording is clear enough to be distinguished from generic get_config, but it does not explicitly name sibling tools like ncloud_serverless_get_config or ncloud_serverless_update_log_config.

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 makes it clear this tool reads log rotation settings for a given clusterName, so its context is clear. It stops short of explicitly stating when not to use it or naming an alternative such as ncloud_serverless_get_config, so the when-to-use guidance is implied rather than explicit.

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