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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description's job is to add behavior — and it does, disclosing the default rate source ('current median pay rate unless a rate is given'). It stops short of saying how the estimate is returned or whether it rounds/assumes anything else.

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 that states the trigger first and the default behavior second. No filler, no restatement of the tool name.

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 zero required parameters and no output schema, the agent gets no guidance on what the tool actually returns (a dollar figure? a view count? both?) or on how to resolve the ambiguity of supplying target and views at once. The description is adequate for triggering but leaves real gaps for correct invocation.

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%, so baseline is 3; the description earns above that by making the two operating modes explicit — target_usd (+period) versus views — and by stating the default rate behavior for rate_per_1k. It doesn't clarify what happens if both modes' parameters are supplied together.

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 states both directions of the calculation: views needed to hit an income goal, and what a given number of views pays. That is a specific verb+resource, but it never names the sibling get_clipping_pay_rates, so the boundary between 'estimate' and 'fetch the rate' is left implicit.

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?

It opens with an explicit trigger ('Use when someone asks...') and gives concrete example phrasings ($100/day, $500/day, $10K/month). There is no explicit when-not-to-use or named alternative, which keeps it short of a 5.

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