Số dư ví MONA Cloud

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

There are no annotations, so the description carries the behavioral transparency burden. 'Đọc' clearly indicates a non-mutating read operation, and the VND/general-wallet scope adds useful precision. It does not describe response format or potential edge cases, but for a zero-parameter read tool this is minimally sufficient.

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?

A single Vietnamese sentence conveys action, resource, currency scope, and the intended timing. Every phrase earns its place, and the core action is front-loaded.

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, parameter-free read-only balance tool with no output schema, this description is complete enough for an agent to decide when and how to invoke it. The purpose, resource, currency, and usage context are all explicit.

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 tool has zero parameters, so there is no parameter documentation burden. The description does not need to explain input semantics, and the schema already reflects no required inputs.

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 uses a clear verb ('Đọc'/'read') with a specific resource ('số dư ví VND chung'/'general VND wallet balance'), and adds a concrete purpose: checking before creating paid resources. It is distinct in intent from financial siblings like cloud_topup and cloud_ledger, though it does not explicitly name or contrast a sibling.

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 states a clear usage context: read the balance before creating paid resources. This gives the agent a concrete trigger for invoking the tool, though it does not explicitly mention when not to use it or suggest alternatives.

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