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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful operational context beyond that: the $0.03 x402 pricing on Base, the x-credit-token prepaid header for unlimited calls, the absence of a free tier, and that no API key is needed — these are auth and rate-limit facts the annotations do not convey.

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 core capability and output before payments logistics, and every section is relevant. There is minor redundancy ('Pass query= ... Required input: query') and slightly promotional phrasing ('bot spam filtering & organic social score'), but no filler that hinders selection.

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?

An output schema exists so return values needn't be spelled out, yet the description still summarizes the score and verdict. Combined with the pricing/auth details and single well-documented parameter, an agent has everything needed to decide and invoke correctly.

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% and the single parameter is fully documented as 'Search query, token or agent ticker'. The description adds only an example value ('HIGHER') and reiterates the required status, which is marginal value over the schema, so the 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?

States a specific verb and resource — measures real-time Farcaster/Warpcast cast velocity and organic momentum for tokens, memecoins, and AI agents on Base. It clearly distinguishes itself from generic social/market siblings by naming the platform (Farcaster) and the unique output (ORGANIC_VIRAL vs ASTROTURFED verdict).

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 a clear context — use it to gauge social momentum for tokens/memecoins/agents on Base — and specifies the required input pattern (query=ticker). It does not, however, name any alternative sibling or state when NOT to use this versus a generic trending/momentum tool, so guidance stops just short of full routing.

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