generateAdmobMediationReport

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

No annotations are provided, so the description must bear full weight. It reveals that revenue values are in micros, which is useful, but omits critical behavioral details such as whether the operation is read-only, required permissions, rate limits, or the report's output format. This is insufficient for safe invocation.

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 extremely concise, using two sentences with no redundant information. The core purpose and the crucial micros detail are front-loaded, making it easy to parse.

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 a complex nested input schema and no output schema, yet the description provides no context on what the report returns, how to interpret results, or the relationship to siblings. It is incomplete for an agent to reliably generate and consume the report.

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 50%, with only metrics and dimensions having descriptions. The description adds the key semantic that revenue values are in micros, which is not in the schema. However, it does not explain other parameter semantics like default metrics or date range restrictions, leaving gaps.

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 performance report. It uses a specific verb 'generate' and resource, and the name differentiates it from sibling report tools like generateAdmobCampaignReport and generateAdmobNetworkReport.

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?

No guidance on when to use this tool versus alternatives like generateAdmobCampaignReport or generateAdmobNetworkReport. The description does not mention prerequisites, exclusions, or typical use cases, leaving the agent to infer context from the name alone.

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