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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful context: status values, deposit tracking, one-wallet-per-person rules, fee responsibility, and the no-airdrop-promise caveat. It does not cover every operational detail, but it goes well beyond the annotations.

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?

The description is dense and clause-heavy, with prerequisite information before the actual purpose is stated. Most sentences add value given the lack of an output schema, but the structure is not tightly front-loaded and some domain exposition could be shorter.

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?

Because there is no output schema, the description needs to explain returned data, and it does so by listing status values, amount, deposit transaction, earnings, and wallet state. It also adds relevant domain constraints, leaving mainly the sibling-tool routing gap.

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%, so the api_key parameter is already documented. The description adds only that register_agent needs no key, which is useful but minor; the baseline of 3 is appropriate when the schema does the substantive parameter documentation.

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 clearly states the resource: the owner's live airdrop farms, including status, amount, deposits, transactions, earnings, and wallet state. It is understandable without opening the schema, but it does not explicitly distinguish this tool from sibling tools such as airdrop_farm_farms.

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 usage by describing what live farm data is shown and by noting the api_key prerequisite, but it does not state when to use this tool instead of airdrop_farm_farms or airdrop_farm_propose_plan. The agent must infer the boundary from the name and description.

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