vechainstats_get_account_vtho_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that this is a read-only operation, whether an address must exist, or any side effects. The mention of data types gives some insight but not enough to fully understand tool behavior.

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?

Single sentence, direct and front-loaded with the action and resource. No unnecessary words or redundancy, making it easy to parse.

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 but lacks an output schema and usage guidance. The description gives useful examples of the returned data, but it does not clarify what the 'expanded' flag changes, nor does it distinguish this tool from similar account stats tools. With no annotations, some gaps remain.

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 covers all parameters with descriptions, providing a baseline of 3. The description adds context about VTHO details (generation rate, accumulated), but it does not explain the 'expanded' parameter beyond the schema's minimal 'Include expanded details', so value added is moderate.

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 detailed VTHO information for an account, with specific examples (generation rate, accumulated). This distinguishes it from sibling tools like get_account_info, which would cover broader account details.

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 implies usage when VTHO info is needed but does not explicitly discuss alternatives or when not to use. It lacks a clear 'use this when' or exclusion statement that would help an agent decide between similar account-related tools.

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