ncloud_cdss_reset_cmak_password

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any side effects, if the operation causes downtime, or whether the reset requires the cluster to be in a specific state. For a reset action, this is a significant gap as agents need to understand impact.

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 short sentence, which is concise. However, it is excessively minimal and lacks structure. It does not front-load key behavioral context, and the extreme brevity suggests under-specification rather than efficient communication.

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?

Given that this is a password reset operation for a cluster, the description lacks critical context: it does not mention if the reset requires the cluster to be running, if there is an immediate effect on connections, or how the password change impacts the CMAK service. With no output schema, the description should compensate, but it does not.

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 coverage is 100% with clear descriptions of both required parameters (cluster instance number and new CMAK password constraints). The tool description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate as the description does not augment parameter understanding.

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 uses a specific verb 'Reset' and clearly identifies the resource 'CMAK access account password for a CDSS cluster'. It is distinct from sibling tools like ncloud_cdss_restart_cmak or ncloud_cdss_get_cluster_detail, so the agent knows exactly what action is performed.

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. It does not mention prerequisites (e.g., cluster state), when not to use it, or contrast with related tools like restart_cmak or change_kafka_config. This lack of usage context leaves the agent without decision support.

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