vechainstats_get_nft_list

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states that the tool gets a list, without mentioning pagination, result limits, response format, rate limits, or whether the list is fully exhaustive in a single call. This is minimal behavioral 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?

The description is a single concise sentence that immediately conveys the tool's purpose. It contains no redundant words or filler, and every word adds value.

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 read-only list, the description is minimally viable but lacks important contextual details such as the shape of the returned data, whether pagination is required, and how it differs from the similarly named 'nft_get_all_collections'. Given no output schema or annotations, some additional context would improve 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?

The tool accepts zero parameters, so there are no parameter semantics to clarify. The input schema is empty and schema description coverage is 100%, leaving no ambiguity. The baseline of 4 applies for a zero-parameter tool.

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's function: retrieving the list of all NFT collections on VeChain. It uses a specific verb and resource. However, it does not distinguish this tool from the similarly named sibling tool 'nft_get_all_collections', which likely serves the same purpose.

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 context about when to use this tool versus alternatives like 'nft_get_all_collections', 'vechainstats_get_nft_info', or 'vechainstats_get_nft_transfers'. There is no guidance on use cases, exclusions, or preference over other NFT-related tools.

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