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

Annotations already establish a safe read-only, closed-world operation. The description adds useful behavior beyond that: scope is limited to tracked airdrops, results cover dates/rules/rewards, the window is recent, and ordering is newest first; it does not describe pagination or result volume.

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?

One front-loaded sentence with no filler; every phrase (tracked airdrops, changed fields, time window, ordering) contributes.

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?

For a single optional-parameter read tool with no output schema, the description supplies the essential scope, time range, content categories, and ordering. Minor gaps are pagination/result-shape details and explicit sibling routing.

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?

The only parameter is fully documented in the schema (integer 1–7, default 1). The description restates the 1–7 day range but adds no syntax or edge-case meaning beyond the schema.

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 the resource (changes in tracked airdrops), the changed attributes (dates, rules, rewards), the look-back window, and ordering. It is specific enough to separate this from a live listing, though it does not explicitly name live_airdrops or history.

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?

Implies use for recent airdrop changes via the 1–7 day window, but gives no explicit when-not or alternative tool guidance (e.g., live_airdrops for current status or history for older changes).

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