Generate AdMob campaign report

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

The description adds meaningful behavioral context beyond the readOnlyHint annotation: the date range restriction and the conversion of monetary metrics from micros to whole currency units. This helps the agent understand data transformations and constraints not evident from the annotation or schema alone.

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 three concise sentences. It front-loads the action and then provides two essential constraints. No wasted words; 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 moderate complexity and lack of an output schema, the description covers the core purpose, key constraints, and metric conversion behavior. It does not describe the exact response format (e.g., CSV, JSON), but the metrics and date range are sufficiently defined. The currencyCode reference and missing output details slightly lower the score.

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%, so baseline is 3. The description adds extra semantic value by explaining that startDate/endDate must be within the last 30 days and that monetary metrics are micro-converted. However, the reference to 'currencyCode' is confusing because this property does not appear in the schema.

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 a report for AdMob cross-promotion campaigns, listing key metrics (impressions, clicks, installs, estimated cost). It distinguishes itself from sibling tools like generate_network_report and generate_mediation_report by specifying 'cross-promotion campaigns'.

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 gives clear context: use this for cross-promotion campaign reports. It also provides an important constraint (date range within last 30 days). It does not explicitly name alternatives or say when not to use it, but the 'cross-promotion' qualifier and sibling names implicitly differentiate usage.

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