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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the bar is lower, yet the description still adds substantive domain behavior: the listing criterion (token has no market and its points/testnet page was read with the programme running), one wallet per person with no pooling, fees paid from the owner's own coins, and an explicit 'No airdrop is promised' disclaimer. Missing only operational traits like rate limits or freshness/caching.

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?

All the content is relevant because there is no output schema to carry the field list, but it is delivered as one long run-on sentence dense with jargon and parenthetical chip codes, making it hard to scan. The core action is front-loaded, but the middle is hard to parse.

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 must carry the return shape and it does: ordering (hottest first), per-farm fields, agent-run flagging, per-$1,000 estimate, and the extra split/range payload when amount_usdc is supplied. Combined with the listing eligibility rules and the no-promise caveat, an agent has everything needed to call it 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 param is self-explanatory, so baseline is 3; the description earns an extra point by explaining the conditional effect of amount_usdc — that it adds the best split over agent-run farms plus a six-month estimate range. That is real semantic value beyond 'the amount to split (optional)'.

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 ('Find airdrop farms') and enumerates exactly what the listing contains: heat 0-100, EARLY chip, agent_runs status, estimate per $1,000. An agent can tell this is the read/list endpoint of the airdrop family. It never names its siblings (airdrop_farm_live, airdrop_farm_propose_plan), so differentiation is left to inference.

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?

Usage is only implied: you call it to browse farms, and supplying amount_usdc additionally yields the optimal split and six-month range. There is no explicit when-to-use statement, no mention of when airdrop_farm_live or airdrop_farm_propose_plan would be the better call, and no prerequisites.

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