get_balance

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by saying 'Get balance' but does not explicitly state that it is non-mutating, has no side effects, or requires no special permissions. For a simple read tool this is a minor gap, but the description adds no behavioral depth beyond the obvious.

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, direct sentence that conveys the essential function with no unnecessary words. It is front-loaded and efficient.

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?

The tool is simple, and the schema covers the parameters adequately. However, there is no output schema, and the description does not mention what the response format will be or that B3TR is also supported. The missing B3TR mention in the description is a notable gap for completeness.

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?

Schema description coverage is 100%, so both parameters (address and tokenSymbol) are already documented. The description adds no additional parameter context and even mentions only VET/VTHO while tokenSymbol supports B3TR, slightly conflicting with the schema without contradicting it outright.

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 gets VET and VTHO balances for an address, with a specific verb and resource. However, it omits B3TR, which is listed as a valid tokenSymbol in the schema, so the description is slightly incomplete and could mislead about supported tokens.

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?

No guidance is provided on when to use this tool versus alternatives like vechainstats_get_vip180_balance or vechainstats_get_account_vtho_info. The description gives no context on preferred use cases or exclusions.

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