vechainstats_get_account_info

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

No annotations are provided, so the description must disclose behavioral traits. It only states what data is returned, not any side effects, failure modes, permissions, or the meaning of the 'expanded' flag. For a read tool this is minimal but not misleading, so a low score is warranted.

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, front-loaded sentence that states the resource and key included data without filler. It earns its place by being brief yet informative enough to convey the core purpose.

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?

With no output schema and no annotations, the description needs to explain what the tool returns. It mentions balances and transaction count, but 'and more' is vague and does not clarify whether it includes staking, VTHO, or other account attributes. The tool is simple, but the ambiguity around 'comprehensive' and 'expanded' leaves gaps for an agent deciding whether to invoke it.

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 the baseline is 3. The description adds no extra meaning beyond the schema for 'address' and 'expanded'. It mentions 'balances, transaction count, and more' but does not clarify what 'expanded' changes, leaving parameter semantics to the schema alone.

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 identifies the tool as retrieving 'comprehensive account information' with specific content ('balances, transaction count'), which is a specific verb+resource+scope. It implies broader coverage than sibling tools like get_balance or vechainstats_get_account_vtho_info, but does not explicitly name alternatives, so it falls just short of full differentiation.

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?

Usage context is implied by the word 'comprehensive' and the tool name, suggesting it is the general-purpose account info endpoint. However, there is no explicit guidance on when to use this tool versus specific siblings (e.g., get_balance, vechainstats_get_vip180_balance), nor any exclusions.

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