cloud_reset_server_password

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

Without annotations, the description carries the full burden. It discloses that the new password is returned, but does not mention side effects like server reboot, termination of existing sessions, or whether the server must be powered on. Adequate but not comprehensive.

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 extremely concise with two pieces of information in one sentence. Every word adds value, and it is front-loaded with the action and constraint.

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 an output schema exists, the description appropriately mentions the return value. However, it lacks information about error conditions, authentication needs, or prerequisites like the server being Linux and the account having sufficient permissions. It is adequate for a simple tool but could be more complete.

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 single parameter 'server_id' has no description in the schema (0% coverage). The tool description does not add any additional meaning beyond its title 'Server Id'. It relies on the obvious purpose, but does not clarify what kind of server ID or any restrictions.

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 states the verb 'reset', the resource 'root password', and the constraint 'Linux only'. It distinguishes from sibling tools like cloud_update_server or cloud_rebuild_server, which do different operations.

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 guidance is given on when to use this tool versus alternatives, such as other password reset methods or server management actions. There is no mention of prerequisites or common use cases.

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