Wallet balance

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that it is a 'point-in-time snapshot' and 'read-only', reinforcing the safe read-only nature. No contradictions; additional context on return fields.

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?

Three concise sentences, each serving a distinct purpose: what it does, what it returns, and when to use alternatives. No redundant information.

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?

Given no output schema, description adequately explains return fields (real and bonus amounts). Also covers scope (Personal Account vs CPA) and related operations. All necessary context for correct invocation is provided.

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?

Parameter schema covers 100% with description; the description restates that user_id is optional and defaults to own account, but adds no new semantic meaning beyond what is in the schema. Baseline score for full coverage is 3.

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 clearly that the tool reads the account wallet balance, specifies the fields (real money and bonus funds in rubles), and distinguishes from CPA balance. The verb 'reads' and resource 'account wallet balance' are specific and unambiguous.

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?

Explicitly tells when to use (Personal Account wallet) and when not to use (CPA balance, history of charges/top-ups). Provides direct alternatives: 'see the cpa domain' and 'use post_operations_history'. Clear guidance for selection.

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