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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real context beyond that — the Base launchpad detection is performed on-chain, and the tool tolerates four identifier types. It omits what happens on a miss (unknown symbol, ambiguous name) and any rate-limit or pagination behavior.

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?

One dense but well-ordered sentence: the returned fields come first, the Base-specific quirk second, and the accepted inputs last. No filler sentences. The long enumeration of return fields is slightly list-like but every item helps an agent decide whether this tool answers its question.

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, enumerating the returned fields was necessary and is done well; the contract-addresses-per-chain and DEX-pool coverage set expectations for shape. Remaining gap is failure behavior for an unrecognized token or an ambiguous symbol, which matters for a lookup keyed on four different identifier types.

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 100% and both parameters are documented, including the chain enum, so the schema carries the load. The description adds a concrete example ('bitcoin') and restates the identifier forms, but says nothing new about the `chain` hint or how ambiguity between a symbol and a name is resolved. Baseline 3 applies.

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+resource ('Full profile for one token') and enumerates the returned surface: price, market cap, FDV, volume, supply, ATH, links, categories, contract addresses, DEX pools, plus Base launchpad detection. An agent can distinguish it from search_tokens or get_launched_token by the breadth of the profile. It stops short of naming which sibling to prefer, keeping it from a 5.

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?

Usage is only implied: agent infers this is the detail-lookup tool for a single token. There is no explicit when-to-use, no when-not, and no reference to search_tokens for discovery or get_launched_token for launch-specific data. The accepted-identifier list helps callers but is parameter information, not selection guidance.

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