Run AdMob mediation report

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds context about the report scope (earnings and performance across mediated sources). While it doesn't elaborate on potential rate limits or data freshness, this is acceptable given the annotation coverage.

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 sentence that front-loads the core purpose and required inputs. It is concise without waste. However, it could be more structured (e.g., separating purpose from usage hints), but remains effective.

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?

Given 10 parameters and no output schema, the description is somewhat brief. It adequately identifies the report type but does not hint at output structure or additional considerations like date range limitations. While schema coverage compensates, more context on report behavior (e.g., pagination) would improve completeness.

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%, with each parameter well-documented including defaults, formats, and allowed values. The description adds minimal extra meaning beyond stating the need for date range, dimensions, and metrics, which is already clear from the schema. Thus 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 focusing on earnings and performance across mediated ad sources. It distinguishes from sibling tools like admob_run_campaign_report and admob_run_network_report by specifying 'mediation' report, making the purpose unambiguous.

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 mentions providing a date range, dimensions, and metrics, which implies usage. However, it does not explicitly guide when to use this tool versus siblings like campaign or network reports, nor does it state prerequisites or exclusions. The readOnlyHint annotation is helpful but not utilized in the description.

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