Generate AdMob mediation report

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

Annotations already indicate readOnlyHint=true, but the description adds valuable context by disclosing that monetary metrics are converted from micros to whole currency units, which is a non-obvious behavior. It also scopes the report to ad sources and mediation groups, giving useful operational context beyond the annotation.

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 two sentences, front-loaded with the main purpose, and includes a useful note about currency conversion. Every word earns its place; no fluff or redundancy.

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?

The tool is complex with 8 parameters and no output schema, but the description covers the core purpose, scope, and key metrics. It does not describe the return format or pagination, but the schema provides parameter details, and the readOnly annotation covers safety. The description is reasonably complete for a report generator.

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 input schema covers all 8 parameters with descriptions (100% coverage), so the description does not need to explain parameters. The description does reference currencyCode and key dimensions, but adds little beyond what the schema already provides. Baseline 3 is appropriate.

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 generates an AdMob Mediation report, specifying the scope (across ad sources, waterfall/bidding) and key metrics (impressions, estimated earnings, observed eCPM). This distinguishes it from sibling tools like generate_network_report and generate_campaign_report by focusing on mediation-specific dimensions and metrics.

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?

The description provides clear context: it is for AdMob mediation reporting, which implicitly signals when to use this tool over network or campaign reports. However, it does not explicitly mention alternatives or state when not to use it, so it falls 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.