generateAdmobCampaignReport

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions the date range constraint, but does not state whether the operation is read-only, what happens if the limit is exceeded, whether it returns report data or a job ID, or any authentication requirements. For a report generation tool, this is insufficient.

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 concise single sentence that front-loads the verb and resource. While it could be slightly more structured, it contains no extraneous information and is 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?

Given the tool's complexity (nested objects, no output schema, no annotations), the description is too sparse. It fails to explain what the report contains, how to handle the date range limit, or what the response format is. More context is needed for effective use.

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 50%, meaning half of the parameters have descriptions. The description adds one key constraint (date range <=30 days) beyond the schema, which provides some guidance on valid input. However, it does not clarify the structure of the dateRange object or suggest typical values for metrics/dimensions.

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 that the tool generates an AdMob campaign performance report, which distinguishes it from sibling tools like listAdmobAccounts or generateAdmobMediationReport. However, it does not explicitly differentiate from similar report-generation tools like 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?

The description only provides a single usage constraint: the date range cannot exceed 30 days. It offers no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. This is minimal guidance.

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