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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), so the description's main added value is disclosing the return shape: campaign, post link, SnapDub status, counting views, and an estimated payout with per-currency totals. The word 'estimated' usefully signals the payout is not final, and 'views that count toward the campaign' signals filtered counting. However, with zero parameters it never says the scope of the listing (all campaigns, all time?), which is a material behavioral gap.

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 dense sentence that front-loads the verb and then enumerates the returned fields, with no filler. It is slightly run-on and bundles payout reporting into what reads as a clip list, which costs a bit of clarity.

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 output schema, the description carries the full burden of explaining return values, and it does enumerate the fields and per-currency totals. What is missing is the scope of the listing given zero input parameters, plus any note on result size or pagination — an agent cannot tell whether this returns everything or a bounded slice.

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 no parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description does implicitly characterize the output fields, but nothing about filtering or scoping is needed because no inputs 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 gives a concrete verb and resource — it lists clips submitted to clipping campaigns along with per-clip status, counted views, and estimated payout — which is specific enough for an agent to know what comes back. It does not reconcile the name/title framing ('earnings') with the fact that the payload is a clip listing, and it never distinguishes this from close siblings like list_clips, get_clip_stats, or get_campaign.

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 when-to-use guidance at all: no statement of which campaigns are covered, whether it is per-user or per-workspace, and no pointer to list_clips or get_clip_stats as the alternative for raw clip data. An agent must infer usage from the field list alone.

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