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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond that: results are ordered by the next hard date, dates come from each project's own docs, and each entry carries a signup link. It does not disclose freshness/update cadence or whether closed campaigns are included, which keeps it below a 5.

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?

A single front-loaded sentence with no filler; the ordering rule and provenance of dates are placed where they are most useful. It reads slightly as a run-on clause stack, but every element (resource, ordering, source, link) earns its place.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does describe the key fields and sort order. It stops short of stating whether only open/active campaigns are returned, how fresh the data is, or how many results to expect, which leaves real ambiguity for a discovery tool.

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 tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify about inputs. It does not wrongly imply filters or options that do not exist.

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 names a specific resource (airdrop and points campaigns) and states it is a listing of 'the campaigns we track,' which is a concrete scope an agent can act on. It does not explicitly contrast with siblings such as signup_link or alerts, but the resource is distinct enough to be recognizable.

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 use this tool versus alternatives like signup_link (which likely retrieves a single link) or alerts (which likely covers notifications). Usage is only implied by the word 'tracked' — the agent must infer that this is the discovery/browse entry point.

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