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

Goes well beyond the annotations by disclosing the paid model ($0.01 per call, USDC), the bearer-credit-key payment path, and the important behavioral quirk that omitting credit_key returns pricing/payment options rather than a report. That fallback behavior is exactly the kind of surprise an agent must know before calling.

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?

Front-loads the most decision-relevant fact (PAID, price) and then covers scope, tier positioning, and payment in four compact sentences. 'Same sources as token-check at a fraction of the price' is slightly promotional but still carries comparative information.

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, the description still characterizes the return as raw data across named sources and flags the alternative return shape when unpaid. It does not describe the output structure or error/failed-payment behavior, which is a modest gap for a paid 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 coverage is 100%, so both address and credit_key are already documented in the schema, and the description largely restates the credit_key semantics ('Pass credit_key to pay ... without it this returns the price'). It adds no syntax or format detail beyond the schema, so the 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 and resource ('Entry-tier token check on Base') and enumerates the exact data covered: GoPlus honeypot, tax, ownership and holder flags plus DexScreener liquidity. It also positions itself against the sibling kairos_token_check ('same sources ... at a fraction of the price'), so an agent can distinguish the tiers without opening either 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?

The description clearly routes the agent: cheap raw-data tier versus the pricier token-check with written analysis, and it states the fallback mode when no credit_key is supplied. It stops short of an explicit 'use X when you need narrative analysis' instruction, but the tier distinction and payment prerequisite are unambiguous.

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