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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations do not: off-chain buy/sell simulation, the return verdict taxonomy, and concrete cost/rate-limit terms (5 free checks/day, then $0.002 via x402 USDC on Base). It omits failure/timeout behavior on unsupported tokens, keeping it short of a 5.

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-loaded with the action and its trigger, then what is tested, then the return shape, then pricing – a logical order with no filler sentences. It is somewhat dense with parenthetical lists, but every clause carries 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 correctly explains the return value (verdict levels plus plain-language reasons), and it covers payment and rate limits. For a one-parameter tool this is nearly complete, though it does not address error or unsupported-token cases.

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 with 100% schema description coverage, so the schema already documents 'address' as a Base token contract address with a hex pattern. The description adds no syntax or format detail beyond that, so the high-coverage baseline of 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?

The description names a specific verb and resource ('check it' a token on Base) and enumerates exactly what is tested: honeypot/hidden-tax simulation, owner powers, whale concentration, liquidity lock, scam lists. It is clearly distinguishable from siblings like check_token_creator (creator vs. token) and check_address_safety (address vs. token) without opening a 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?

It gives explicit timing guidance ('Before buying a token on Base, check it'), which tells the agent the triggering context. However, it never names the sibling tools or states when to prefer check_token_creator or check_address_safety instead, so routing among alternatives is left to inference.

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