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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real value beyond that by enumerating the returned fields (price, market cap, 24h volume, price changes) and clarifying that results are standard ERC20s, which enables correct follow-up via baseSwap. It does not explain pagination behavior for limit/offset or any rate limits.

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?

Four short sentences, front-loaded with the resource and source, then search/sort mechanics, then the cross-tool handoff. Every sentence carries information an agent needs and there is no 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?

With no output schema, the description does cover the shape of returned token data, and it routes write intent to baseSwap. However, for an 8-parameter, zero-coverage schema it leaves most parameters undefined, so an agent cannot confidently set pagination, chain, or inclusion flags from this description alone.

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 0% across 8 parameters, so the description carries the full documentation burden. It explains only 'q' (search by name/symbol) and the sortBy values (market-cap, created-at); limit, offset, chainId, sort direction, includeUser, and includeMarket are undocumented in both the schema and the description.

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 (Find), resource (meme tokens), chain (Base), and the defining source (Clanker / clanker.world). This cleanly separates it from siblings like bscfindMemeCoinsViaFourMeme, hederaFindMemeCoins, getPumpFunTokens, and findSolanaGems 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?

Gives concrete routing: use 'q' to search by name/symbol, and explicitly redirects buy/sell intent to baseSwap with the reason (they are regular ERC20s on Base). It lacks an explicit 'when not to use this' or guidance on choosing between sortBy options, but the usage context is clear.

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