Danh sách service MONA Cloud

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is covered. The description adds meaningful context beyond annotations: sandbox=true includes 0-cost trial services and the API call needs no header. It does not contradict the annotations.

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 a single front-loaded sentence with no wasted wording. It states the resource listed and the sandbox behavior efficiently.

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 read-only list tool with full schema coverage and annotations, the description covers the core behavior and sandbox flag. It could still be more complete by mentioning sibling alternatives or listing order/pagination, but the essential invocation details are present.

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 sandbox parameter is already documented in the schema. The description still adds value by explaining that sandbox=true merges in trial 0-cost services and that no header is required, going slightly beyond the schema's 'thử 0đ, không cần ví' wording.

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 gives a specific verb and resource: 'Liệt kê VPS/database' (list VPS/database), so the agent knows this is a list operation for cloud compute and database services. It also clarifies that sandbox=true includes trial 0-cost services. However, it does not distinguish this tool from nearby siblings like cloud_services or vibecloud_list_services.

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 gives parameter usage context for sandbox=true, but it does not say when to choose this tool over alternatives such as cloud_services or vibecloud_list_services. There are no when-not conditions or routing guidance.

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