adsense_generate_report

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

No annotations are provided, so the description carries the behavioral burden. "Extract" implies a read-only data fetch, and "Account is discovered automatically when omitted" is a useful behavioral detail. However, it does not disclose response format, pagination behavior, permissions, or any side effects, leaving a meaningful transparency gap.

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?

Two front-loaded sentences say exactly what is needed without fluff. The first sentence gives the purpose, the second tells the caller what to supply and clarifies account optionality.

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 12 parameters, no output schema, and no annotations, this description is too thin. It does not say what the report response looks like, whether results are paginated, or how ad-hoc complexity is handled. The auto-discovery note is helpful, but the tool still lacks guidance for an agent to fully anticipate the invocation outcome.

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 75%, and the description adds a high-level parameter map: dimensions, metrics, filters, dates, sorting, and other report parameters. It also notes the API version, which helps normalize parameter syntax. It does not detail every uncovered parameter such as limit, currencyCode, or languageCode, but the schema still provides most semantics.

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 opens with a specific verb and resource: "Extract any ad-hoc AdSense report." It clearly distinguishes this reporting tool from the sibling account tools by framing it as report extraction with flexible parameters.

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?

It gives clear context: use this tool for ad-hoc AdSense reporting where the caller supplies dimensions, metrics, filters, dates, and sorting. It also removes a common prerequisite by noting that the account is discovered automatically when omitted. It does not explicitly compare to sibling alternatives, but the usage context is clear.

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