airdrops

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

Discloses caching (~1hr), manual content revision, and hand-verified entries; no annotations, so description effectively communicates read-only nature and update behavior.

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?

Two sentences with essential details, no redundant information; front-loaded with core purpose and key attributes.

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?

Sufficient for a no-parameter tool; covers content, freshness, and caching; only minor gap is lack of mention of output format or size limit.

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?

No parameters; description adds meaning about the returned data (chain, status, eligibility) beyond the empty 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?

The description clearly states the tool returns curated active and upcoming crypto airdrops, distinguishing it from sibling tools focused on market stats.

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?

Context is clear for fetching airdrops, but no explicit when-not-to-use or alternatives; sibling differentiation is implied by distinct tool purposes.

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