hedera_get_token_info

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

With no annotations, the description carries full burden. It indicates a read operation via 'Read' and specifies the source, but does not disclose potential rate limits, data freshness, or authentication requirements. Adequate but not rich.

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 one clean sentence, front-loaded with the verb, and every word adds value. No 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?

The tool has no output schema, so the description should describe the return. It lists key fields (type, supply, keys, custom fees) but omits others like owner or metadata. Adequate for a simple read, but could be more thorough.

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 coverage is 0% and the description adds no information about the single parameter 'tokenId'. The parameter name is self-explanatory, but the description should specify format expectations (e.g., '0.0.1234'). This is a critical gap.

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 a specific verb ('Read'), resource ('token info'), and lists key fields (type, supply, keys, custom fees). It also mentions the source ('Mirror Node'), effectively distinguishing it from sibling tools like hedera_get_token_balances or hedera_get_nft_info.

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?

While the description implies a read-only query, it provides no explicit guidance on when to use this tool versus alternatives (e.g., hedera_get_token_balances for balances). No exclusions or prerequisites are mentioned.

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