Change root password

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

Annotations declare destructiveHint=true but say nothing about the operation's side effects. The description adds meaningful context: the password format constraints, the required permission scope, and the full-access key requirement. It does not state whether the old password is invalidated or the service restarted, so it stops short of full disclosure.

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?

Three short sentences, no filler, front-loaded with the action and immediately followed by constraints and prerequisites. Every sentence carries information the caller needs.

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 2-param mutation with no output schema, it covers action, constraints, example, and auth prerequisites. The one gap is what happens to the instance afterward (e.g., whether a reboot or session invalidation occurs), but the core invocation needs are met.

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%, so the schema documents both parameters; the description nonetheless restates the password rules with a concrete example ('MyPass123'), which is useful for constructing a valid value. It adds no new meaning for orderNo, but the password guidance has practical value.

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?

Specific verb+resource ('Change VPS root password') with no ambiguity, and 'VPS' plus 'root' clearly distinguish it from the many networking/SSL sibling tools. An agent can identify this as a server credential mutation immediately.

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 states prerequisites (services:manage, full-access API key) but gives no explicit when-to-use vs alternatives guidance. Since no sibling tool changes root passwords, the risk of misrouting is low, but the description relies on that inference rather than stating it.

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