ncloud_set_server_log_collection

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: it returns an agent install key and an install command that must be run on each target server, which tells the agent this is a two-step provisioning flow, not a fire-and-forget mutation. It doesn't address permissions or how to undo the configuration.

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?

Two short sentences, zero filler, with the operation and its return payload front-loaded. Nothing is repeated from the name or schema.

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 no output schema, the description usefully discloses the return payload, and parameters are fully documented in the schema. What's missing is the surrounding workflow: that server metadata should first be retrieved from ncloud_list_log_servers and how the returned install key is used.

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%, including per-field notes like 'from ncloud_list_log_servers', so the schema carries the parameter burden. The description adds no syntax, format, or default information beyond what the schema already provides, which is the expected baseline when the schema is this complete.

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 verb and resource ('Configure log collection on VPC servers'), names the service context (Cloud Log Analytics), and even says what comes back (agent install key + install command). It is clearly distinct from sibling log-query tools like ncloud_search_logs or ncloud_list_log_servers, though it never names a sibling explicitly.

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 when-to-use, when-not, or prerequisite guidance appears in the description. The schema hints that servername/macAddr/osType come from ncloud_list_log_servers, but that workflow dependency is not stated in the description where an agent would look for routing advice.

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