vechainstats_get_token_supply

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states the basic read action without mentioning response format, pagination, error cases, or anything about the expanded parameter's behavior. For a read tool, the absence of side effects is implied but not stated, and no other behavioral context is given.

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 filler or redundant information, and the key verb and object are front-loaded.

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 with only two parameters and no output schema, so the description's brevity is somewhat acceptable. However, it lacks usage guidance and for a tool without an output schema, it does not fully describe return values beyond listing 'total, circulating' as examples. It is adequate but not 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 fully documents both parameters ('token' and 'expanded'), so schema coverage is 100%. The description does not add any new parameter-specific meaning beyond what the schema already provides, earning the baseline score of 3.

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's action ('Get') and resource ('token supply information'), with specifics like total and circulating supply. This distinguishes it from sibling tools like get_token_info and get_token_price, which focus on other aspects of tokens.

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 its usage for retrieving token supply data but does not explicitly state when to prefer it over alternatives or provide exclusions. There is no mention of when to use expanded details or how it relates to sibling tools, so usage context is only implied.

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