Generate AdMob network report

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds a valuable behavioral detail: monetary metrics are converted from micros to whole currency units (see currencyCode). This goes beyond the schema and annotations, though it does not disclose pagination or return structure.

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 long, front-loaded with the core purpose, and contains no redundant or filler content. Every sentence provides useful information.

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 has 8 parameters and no output schema, yet the description does not explain the return format, pagination behavior, or defaults beyond what the schema provides. It covers core purpose and a key unit conversion, but leaves gaps in expected output and usage context for a complex reporting tool.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that currencyCode affects the conversion of monetary metrics from micros to units, which clarifies the parameter's behavioral impact. Other parameters are not individually elaborated, but the schema already covers them.

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 uses a specific verb ('Generates') and clear resource ('AdMob Network earnings/performance report'), and lists concrete metrics (requests, impressions, clicks, estimated earnings, match rate, RPM). It also distinguishes itself from sibling tools like generate_mediation_report and generate_campaign_report by specifying 'Network'.

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 scope is implied by 'AdMob Network report', which suggests it is for network-level data rather than mediation or campaign reports. However, the description does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites.

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