solana_get_token_info

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

No annotations provided, so description carries full burden. Describes high-level action but does not disclose return format, permissions needed, or whether it is read-only. Contradiction between 'any SPL token' and empty input schema is unexplained.

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?

Single sentence, front-loaded with main action, no wasted words. Every part is informative.

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?

Given absence of input parameters, description fails to explain how the tool selects a token. No output schema or behavioral details. Major context missing for a tool that claims to fetch metadata for 'any' token.

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?

No parameters in input schema (0 params) so baseline is 4. Description adds value by specifying output fields (decimals, supply, authorities) beyond schema. However, it does not clarify how the tool identifies the token without parameters.

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?

Clearly states verb 'get' and resource 'on-chain metadata for SPL token', listing examples like decimals, supply, authorities. Lacks explicit differentiation from sibling tools like solana_get_token_balance, but the purpose is specific enough.

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 guidance on when to use this tool vs alternatives. No prerequisites or context for usage (e.g., requires a token address, but input schema has no parameters). Implied by name but not explicit.

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