rebuild service MONA Cloud

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

With no annotations, the description carries full behavioral disclosure burden. It usefully warns that the command can incur costs, advises checking the wallet, and explains that sandbox=true is free and wallet-free. However, it does not disclose whether rebuilding destroys existing data or causes downtime, which is significant for a rebuild operation.

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 compact and well-structured: purpose first, then the cost warning, then the sandbox clarification. Every sentence earns its place, and there is no redundant filler.

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 potentially costly and destructive operation with no output schema and no annotations, the description omits important context: what rebuild actually does to the service, how to obtain a valid service_id, and whether there is a way to track completion. The cost and sandbox notes are helpful, but safe invocation still requires significant inference.

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 only 50%, and the description only repeats the sandbox parameter's schema text. The service_id parameter, which is required, receives no semantic explanation beyond its name. The description fails to compensate for the undocumented parameter.

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 states a specific verb ('rebuild') and resource ('VPS/database MONA Cloud'), making the core operation clear. It is distinguishable from start/stop tools by the rebuild verb, though it does not explicitly differentiate from the closely related sibling vibecloud_rebuild.

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 operational caveats about cost and sandbox mode, but gives no guidance on when to prefer this tool over alternatives like cloud_service_start, cloud_service_stop, or vibecloud_rebuild. There is no clear 'use this when...' statement.

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