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

No annotations are present, so the description carries the burden; 'Read' implies a non-mutating operation and the second sentence usefully discloses that Solana results include mint and freeze authority fields, which other chains do not. It does not say how invalid addresses, unsupported mints, or rate limits are handled, so the behavioral picture is only partly filled in.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence could be tightened into a chain-qualified clause, but nothing is wasted.

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?

With no output schema, the description compensates by naming the returned fields, which is exactly what an agent needs to know before calling. The main omission is sibling disambiguation against check_token, which is a routing rather than completeness gap.

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 description coverage is 100% and the chain enum is fully documented, so the schema already carries parameter meaning. The description adds a small amount by implying that return fields vary by chain, but it does not map that variation onto the required parameters explicitly.

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?

States a specific verb and resource ('Read a token's on-chain details') and enumerates exactly which fields are returned, including Solana-specific ones. It does not, however, distinguish itself from the sibling check_token, which an agent could easily mistake for this tool.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the sibling check_token (presumably a risk/safety check). The description reads as a definition rather than a routing rule, leaving the agent to infer which of the two token-related tools to call.

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