ncloud_cdss_restart_all_services

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

Annotations indicate idempotentHint=true and destructiveHint=false, so the agent knows the operation is safe and repeatable. The description adds the scope of services restarted. However, it does not disclose potential behavioral traits such as whether the restart causes downtime, how long it takes, or if it is synchronous. With annotations covering the safety profile, the description provides minimal extra value.

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, well-structured sentence that front-loads the key information. Every word is meaningful, and there is no redundancy or unnecessary detail. It exemplifies conciseness.

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 tool that restarts multiple services, the description lacks important context. It does not mention return values (no output schema), whether the operation is asynchronous, or any prerequisites (e.g., cluster must be running). Given the complexity and the existence of a rolling restart sibling, more detail would be beneficial for correct agent invocation.

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 has 100% description coverage for the only parameter ('serviceGroupInstanceNo' with description 'Cluster instance number'). The tool description does not mention this parameter or provide any additional meaning beyond the schema. Baseline 3 is appropriate as the schema already carries the semantic load.

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 specifies the action ('Restart all services') and the resource ('in a CDSS cluster'), listing the exact services (Kafka, ZooKeeper, CMAK). It distinguishes itself from sibling tools like ncloud_cdss_restart_kafka and ncloud_cdss_restart_cmak, leaving no ambiguity about scope.

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 implies when to use this tool (when you want to restart all services in a CDSS cluster), and the scope is clear. However, it does not explicitly state when not to use it or mention alternatives like rolling_restart, which could be relevant for less disruptive restarts. Still, the context is strong enough for an agent to infer appropriate use.

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