vechainstats_get_token_list

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 mentions 'comprehensive' and 'metadata' but does not disclose any behavioral traits such as response size, pagination, performance implications, or data freshness. For a list endpoint, at least noting the potential for a large payload or rate limits would add transparency.

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?

A single sentence that is front-loaded and contains no filler. It earns its place by conveying the core purpose and scope without 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?

For a zero-parameter tool, the description is minimally viable but lacks detail about the return value. 'With metadata' is vague—unclear whether it includes token address, symbol, decimals, total supply, etc. Given no output schema and no annotations, a brief elaboration on the metadata fields or the nature of the response would make it more complete.

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 input schema has zero parameters, and the description accurately reflects a no-argument list operation. Per the baseline, with 0 params the description need not elaborate on parameter semantics. The term 'comprehensive list' also implicitly signals that no filters are applied.

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 uses a specific verb ('Get') and clearly identifies the resource ('comprehensive list of all tokens on VeChain with metadata'). It distinguishes from sibling tools like vechainstats_get_token_info (single token) and vechainstats_get_all_token_prices (prices only) by emphasizing the comprehensive list scope.

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 explicit guidance on when to use this tool vs alternatives. With many token-related sibling tools (e.g., get_token_info, get_token_price, token_exists), the description does not clarify that this is for the full list, not for queries about a specific token.

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