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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the categories of data returned (metadata, market cap, curve status), but says nothing about freshness, caching, rate limits, or failure behavior for an unknown mint. It adds context but is not rich beyond the annotation baseline.

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 sentences, no filler, and the core purpose is front-loaded ahead of the disambiguation clauses. Every clause earns its place by either defining scope or routing to a sibling.

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?

For a one-parameter read tool with no output schema, the description covers both what the tool takes and what it returns at a category level, plus alternatives. Minor gap: it does not say what happens when the mint is unknown or whether results are cached/live, which an agent might need for a fresh-lookup tool.

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?

There is a single parameter (mint) and schema description coverage is 0%, so the description carries the burden. It clarifies that the parameter is a token mint address rather than, say, a symbol or pair address, which is genuinely useful — but it gives no format, validation, or example (e.g. base58 length), so it only partially compensates.

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 (retrieve full details), a specific resource (a pump.fun token), and the lookup key (mint address). It also names the two sibling tools it must not be confused with, so an agent can distinguish it without opening any schema.

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?

Explicitly states the precondition ("when you already have a mint") and what you get (metadata, market cap, curve status), then routes the agent away with two named alternatives: get_token_holders for holder concentration and get_token_trades for recent fills. When-to-use and when-not-to-use are both covered.

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