Uninstall Monarx

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

With annotations already marking this destructive (destructiveHint=true) and idempotent (idempotentHint=true), the description adds a useful edge case: 'If Monarx is not installed, the request will still be processed without any effect.' This goes beyond what the structured hints alone convey.

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 first two sentences are front-loaded and useful; the third sentence largely repeats the first. Still, the entire definition is compact and easy to scan.

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 one-parameter tool with annotations carrying the destructive/idempotent safety profile and no output schema, the description covers what the tool does, the target virtual machine, and the no-op case. Nothing essential is missing for correct 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?

Schema description coverage is 100%: the single parameter virtualMachineId is already described as 'Virtual Machine ID.' The description only restates 'a specified virtual machine' and adds no parameter-level semantics beyond the schema.

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?

States a specific verb+resource: 'Uninstall the Monarx malware scanner on a specified virtual machine.' It clearly differentiates itself from the nearby install operation by naming the product and the action, so an agent can tell it apart from VPS_installMonarxV1.

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 final sentence gives explicit context: 'Use this endpoint to remove malware scanner from VPS instances.' It does not explicitly name alternative tools or exclusion conditions, but for this tool the intended use is unambiguous.

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