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

The description explicitly claims 'Read-shaped tools only (anything that buys, sells or writes refuses)' and says 'their data comes back as it is,' indicating a read-only, pass-through behavior. However, the annotations set readOnlyHint to false, which contradicts the description's clear read-only claim. This is a serious annotation contradiction.

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 first sentence is strong and front-loads the core purpose. However, the second sentence contains a malformed fragment ('Where the — Singularity Agent's MCP server...') and the listing URL adds extra noise, making the description less crisp than it could be.

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 explains the return concepts (name, ticker, metadata link, mutability) and the pass-through nature of the data, which partially compensates for the missing output schema. But with no formal parameters and no output schema, it leaves a critical gap: how the agent specifies which Solana mint to read. The contradictory readOnlyHint also undermines completeness.

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 tool has zero formal parameters and 100% schema description coverage, so the baseline is 4. The description adds useful semantic context by naming the Solana mint domain and the kinds of identity data returned, but it does not clarify how the target mint is selected when no parameters are defined.

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 the tool 'Read what a Solana mint says it is' and specifies the exact outputs: name, ticker, metadata link, and whether that metadata can be rewritten at the same address. This is a specific verb+resource pairing that uniquely distinguishes token_identity from related Solana tools like read_contract or decode.

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 intended use is implied by the first sentence: inspect a Solana mint's identity and mutability. However, the description never names alternative tools or states explicit when-to-use vs. when-not-to-use conditions, so the agent is left to infer routing from the purpose alone rather than from clear guidance.

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