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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered. The description adds genuine value beyond them: the data source (Hedera mirror node), the HIP-904 semantics (receiver needed no pre-association), and the promise of an "honest empty result" rather than an error when nothing is pending.

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 verb and resource, and the parenthetical plus trailing sentence each contribute real information about the tool's semantics. It stays to two clauses without filler, though the em-dash aside is slightly dense.

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 required parameter with 100% schema coverage and annotations covering safety, the description is nearly sufficient. It describes what the returned items are (tokens/NFTs awaiting claim) and empty-result behavior, which compensates for the absent output schema, though the exact response shape/pagination remains unspecified.

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 account_id parameter is fully documented including an example, so the schema carries the load. The description only implies filtering by account and adds no format or syntax detail beyond the schema, which is the baseline-3 case.

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 gives a specific verb+resource ("List an account's pending HIP-904 airdrops from the Hedera mirror node") and clarifies what those airdrops are. It does not explicitly name or contrast with the adjacent sibling tools (prepare_airdrop, check_claim_status), so the differentiation is implied by the resource rather than stated.

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?

There is no statement of when to reach for this tool versus alternatives like prepare_airdrop (creating) or check_claim_status (claiming). The description explains what pending airdrops are but offers no usage context, prerequisites, or exclusions.

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