Get account balance

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

Description adds detail beyond annotations (readOnlyHint, openWorldHint) by stating it returns balance in RUB and can_payout for partner status. No contradictions; simple read operation fully disclosed.

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 sentences, front-loaded with primary function, then usage advice. Every sentence adds value with no redundancy.

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?

Fully adequate for a zero-parameter read-only tool. Covers purpose, return value components, and usage context. No output schema needed.

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?

No parameters; baseline 4. Description adds meaning by explaining what the return value contains (main funds, can_payout) though no param info needed.

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?

Description specifies it returns current account balance in RUB plus optional can_payout amount, with clear verb-resource pair 'returns balance'. Distinguishes from sibling tools like buy_proxy.

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 instructs to use BEFORE buy_proxy to confirm sufficient funds, and warns that buy_proxy will fail with 'Insufficient balance' otherwise. Provides clear when-to-use and consequence.

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