Баланс аккаунта

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds marginal value by specifying the return fields (Amount, Currency) and API version. It does not disclose permissions, side effects, or behavior beyond what annotations provide, warranting a moderate score.

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 sentence that conveys the essential purpose without unnecessary words. It is front-loaded and structurally optimal for an agent to parse quickly.

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 the tool's simplicity (one optional parameter, no output schema, read-only annotations), the description adequately covers the core functionality. It lacks details like default behavior when 'logins' is omitted or the format of amount/currency, but these are minor given the context.

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 single parameter 'logins' is fully described in the schema (100% coverage), and the description does not add further semantic meaning. Baseline score of 3 is appropriate since the schema carries the burden.

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 clearly states the tool retrieves balance and financial information (Amount, Currency) via Live API v4. It uses a specific verb-resource pair, but does not explicitly differentiate from sibling tools, though the read-only nature distinguishes it from management siblings.

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 provides no guidance on when to use this tool or when to avoid it. No alternatives are mentioned, and the parameter description for 'logins' is only in the schema. The absence of usage context leaves the agent to infer its application.

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