Get MoMo account balance

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

Annotations already declare readOnlyHint=true, so the trailing "Read-only" is pure repetition of structured data. The only added detail is that the account is "configured" (no account id parameter), but nothing is said about network/auth failure modes despite openWorldHint, or about what the balance represents.

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?

Two short sentences, front-loaded with the action. The second sentence is wasted words because it restates the readOnlyHint annotation, costing a point.

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 zero-parameter read this is close to sufficient, but with no output schema the description never says what the balance result contains (currency, available vs. current balance) or that an error occurs when credentials are not configured. A sentence on the return shape would close the remaining gap.

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 takes no parameters, so there is nothing for the description to compensate for; the baseline for a zero-parameter tool applies.

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 and resource ("Read the balance of the configured MoMo account"), which is clearly distinct from siblings like momo_check_account_active or momo_verify_credentials. It does not explicitly differentiate itself from those siblings, but the resource noun does most of that work.

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?

There is no statement of when to call this versus momo_check_account_active, momo_verify_credentials, or momo_environment, and no preconditions (e.g., credentials must be configured first). Usage is only implied by the name and the word "configured".

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