AdMob mediation report

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral details: monetary values are pre-divided from micros, and only one time dimension permitted. No contradictions with annotations.

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 moderately concise, front-loaded with purpose, and enumerates dimensions/metrics clearly. It could be slightly shorter but every sentence adds value.

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 the complexity of 11 parameters and no output schema, the description covers key aspects: purpose, available dimensions/metrics, time dimension constraint, and monetary value format. It does not detail return structure beyond raw/table, but the 'raw' parameter addresses that.

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 coverage is 100% with per-parameter descriptions. The description adds value beyond the schema by explaining constraints (only one time dimension) and data format (monetary values pre-divided), which are not obvious from the schema alone.

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 for per ad-source revenue and performance, and lists allowed dimensions and metrics. This verb+resource combination is specific and distinguishes from siblings like admob_network_report, which likely focuses on network-level data.

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 usage context by stating that only one time dimension (DATE/MONTH/WEEK) is allowed per request and defines default metrics. However, it does not explicitly exclude sibling tools or specify when to use this tool versus alternatives like admob_network_report.

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