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

With no annotations, the description carries the full burden and does so: it discloses pricing ($0.02/call from shop credits, top-ups paused), that failed or empty calls are free, the 404 behavior below the follower floor, and the strong vs. weak (exact address vs. cashtag) match semantics — exactly the behavioral context an agent needs before spending credits.

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?

A single dense paragraph that front-loads what you get back before cost and failure semantics; every clause carries information, though the list of return fields is slightly run-on and cost/credit terms could be separated for scannability.

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 and no annotations, the description fully compensates: it enumerates the response fields (handle, followers, verified, post count, first_call_at, kol_count, total_reach, buzz label, price change), lists supported chains, and explains cost and empty-result behavior.

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% with enums and defaults already documented, so the baseline is 3. The description adds only marginal semantics — the 8-chain scope and the existence of a follower floor — and says nothing about the 'window' parameter or how min_followers interacts with the 404 rule.

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 opens with a specific verb+resource framing ('send a token contract, get the big X/Twitter accounts posting about it, ranked by followers') and enumerates the returned fields, so an agent can distinguish it from siblings like token_smart_money, token_holders, or x_search without opening the 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 implies the usage context (token-level X/Twitter KOL buzz for a given contract) and states the empty-result condition, but it never names an alternative tool or says when to prefer token_smart_money / x_search / token_verdict over this one.

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