Uninstall Malware Scanner

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

No annotations are provided, so the description must disclose behavioral traits. It only restates the removal action without mentioning side effects, reversibility, or requirements. It does not warn that this is a destructive operation or whether the VPS needs to be stopped.

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?

One concise sentence with no wasted words. It is direct and front-loaded, clearly stating the action and target.

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 simple one-parameter removal tool, this description is minimal but adequate. It lacks behavioral context (e.g., whether the VPS must be offline, whether the action is irreversible) and no output schema exists, so an agent may not know what to expect.

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 vm_id is fully documented in the schema (type, description, required). The description adds no further parameter meaning, but baseline holds at 3 due to 100% schema coverage.

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 a specific verb ('Remove') and a specific resource ('Monarx malware scanner from a VPS'). This distinguishes it from sibling tools like vps_malware_install and vps_malware_metrics.

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 purpose implies usage for uninstalling the scanner, but no explicit when-to-use or alternative guidance is given. It does not state prerequisites (e.g., VM must exist) or contrast with install/metrics beyond the obvious opposite.

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