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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them: data sources (DexScreener pool, GoPlus contract checks, Go+ Security), the constraint that a red flag is repeated only when a check actually raised it, the return payload (roast, facts, 1200x630 PNG card with share-linked preview), and the 'never a buy or sell signal' disclaimer.

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?

Usage guidance is front-loaded and each sentence carries new information (persona, sourcing, constraint, return shape, disclaimer). It is dense with parentheticals and could be trimmed, but nothing is pure filler.

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?

There is no output schema, so the description correctly takes on the burden of describing returns (roast text, supporting facts, shareable PNG card). Combined with the data-source and red-flag-repetition disclosures, an agent has everything needed to call and interpret this 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?

Schema description coverage is 100% and both parameters are documented there, so the baseline is 3. The description adds no syntax or format detail for address or quote beyond what the schema already gives.

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 (roasts) and resource (an EVM token), names the persona (SWOGE the shiba inu), and explicitly anchors itself to the sibling token_verdict as the serious counterpart. An agent can distinguish it from token_verdict, scan_token, and robinhood_token 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 frames the use case ('when you want a funny, shareable take ... for a post or a chat') and implicitly scopes it away from serious analysis by saying the facts match token_verdict. It never states a when-not explicitly, but the entertainment framing makes the boundary clear.

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