vechainstats_get_token_info

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only lists return content (supply, holders, metadata) and does not disclose effects of the 'expanded' parameter, error behavior, or any operational constraints. This is a read operation but that is implicit via 'Get', not elaborated.

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, front-loaded sentence that states the action and key information categories. There is no redundancy or unnecessary detail, making it efficient and 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 description gives a sense of the return content ('supply, holders, metadata') but is incomplete for a tool with no output schema. It omits details about the 'expanded' parameter and does not clarify what 'metadata' entails, leaving ambiguity for agent invocation.

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 already provides 100% coverage, including descriptions for both 'token' and 'expanded'. The description adds no additional meaning about parameter usage or formatting, so it meets the baseline without improvement.

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 clear verb 'Get' and identifies the specific resource 'detailed token information' with concrete aspects (supply, holders, metadata). This distinguishes it from sibling tools that focus on individual aspects like supply or holders.

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 this tool is for comprehensive token information but does not explicitly state when to use it over alternatives like vechainstats_get_token_supply or vechainstats_get_token_holders. No exclusions or alternative references are provided.

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