Page revenue (AdSense + Search Console)

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add semantics — and it does: 'Earnings cover all traffic to the page, not only search' is a genuine caveat that prevents misinterpretation, and the flag definitions disclose how results are selected. It stops short of describing pagination or rate limits, so it is strong but not exhaustive.

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 compact sentences, front-loaded with the core join before the flagging detail, and the traffic-scope caveat is placed where it cannot be missed. No filler.

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 and six parameters, the description carries part of the return-value burden and does so conceptually (a per-URL earnings-plus-performance join with opportunity flags), plus it explains the default date window indirectly through the schema. Missing only concrete output shape/pagination, which is a minor gap.

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 description coverage is 83%, so the schema already documents siteUrl, account, date defaults, and minPageViews. The description adds no parameter-level detail, leaving the baseline 3 appropriate for a schema-rich tool.

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?

It names a specific operation and two distinct data sources: joining AdSense per-page earnings with Search Console performance for the same URLs, then flagging revenue opportunities. That is far more than a restatement of the name, but it never explicitly distinguishes itself from adjacent siblings such as page_performance or find_opportunities, so an agent must infer the boundary.

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?

Usage is implied rather than stated: the flagging criteria (above-median RPM ranking 8–20, low CTR for position) tell the agent this is the revenue-oriented view, but there is no explicit when-to-use/when-not guidance and no named alternative against which to choose it.

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