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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds valuable context by listing the exact data returned and noting the tool is 'Public', which goes beyond annotation coverage. It doesn't mention caching, latency, or rate limits, but for a read-only stats tool this is sufficient.

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?

The description is a single, well-structured sentence with the primary purpose ('live state') front-loaded, followed by a clear list of return items. Every phrase adds information; no wasted words.

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 parameterless read-only tool with no output schema, the description fully specifies what the agent can expect: revenue, parked pool, publisher count, top reporters, last round, and payout status. It also signals public access. Nothing an agent needs to call it correctly is missing.

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?

There are zero parameters, so the description has no need to explain them. Per the rubric, 0 params warrants a baseline of 4. The description doesn't introduce any misleading parameter references.

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 provides a live snapshot of the ad network, enumerating specific data points (settled revenue, parked pool, publisher count, top reporters, last round, payout status). This distinguishes it from sibling tools like adnet_rounds (round history) or adnet_feed (likely feed content), even without explicit comparison.

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?

No explicit guidance on when to use this tool versus alternatives. The description mentions 'Public' which may imply accessibility, but it doesn't state 'use this for a quick overview' or contrast with adnet_report or adnet_rounds. Usage context is implied but not spelled out.

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