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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds exactly the context they cannot: pricing ($0.04/call over x402 on Base), the auth path (prepaid x-credit-token header or no API key), and the rate limit (1 free call/day per tool). That is auth, cost, and quota behavior disclosed up front.

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 scoping and payment facts are front-loaded and every functional sentence earns its place. The opening rhetorical question ('Who created this token — and can you trust them?') is promotional filler that costs a line without adding invocation guidance.

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 an output schema present, the description needn't detail return values, and it still summarizes the score-plus-signals shape. The one real gap is that 'address' is not tied to a chain, which matters in a toolset with base_, near_, and b20_ siblings.

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 required parameter with 100% schema description coverage ('Token contract address'), and the description only restates 'Required input: address'. The schema does the heavy lifting, so the baseline 3 applies; no format or chain-of-address detail is added.

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 gives a specific verb and resource: it profiles the token's creator/deployer wallet and rolls history, retained supply, and renounce status into a 0-100 reputation score with signals. That is far more precise than a generic 'reputation' label and separates it in spirit from rug_score or address_intel. It does not name a sibling tool explicitly, so it stops short of 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?

It supplies a clear decision context — 'a fresh wallet holding 20% of supply with no renounce is the classic rug setup' — which tells the agent when this check is worth spending on, and it states the required input. It offers no explicit when-not-to-use or named alternative tool, so no exclusions are present.

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