generate_report

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation ('generate') and resource ('AdSense earnings report'), which strongly implies a read-only action, but it does not explicitly disclose side effects, permission requirements, output format, or whether data is live vs cached. This leaves significant room for agent uncertainty.

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 single, efficient sentence with the core action front-loaded. Every phrase earns its place: the resource is named, and the customizable aspects are listed without fluff or repetition.

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 no annotations and no output schema, the description provides adequate context for the tool's purpose and parameter capabilities, but it omits information about the output format, return structure, or any limitations. An agent can invoke it with defaults, but may not know what to expect in the response. The parameter schemas fill most gaps, yet the absence of output guidance leaves it a minimum-viable description.

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 100%, so the baseline is 3. The description's mention of 'date range, metrics, and dimensions' merely echoes the schema properties without adding new meaning. It does not clarify enum semantics, units, or how parameters interact beyond what the schema already provides.

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 uses a specific verb ('Generate'), a clear resource ('AdSense earnings report'), and states the customizable dimensions ('date range, metrics, dimensions'). This distinguishes it from sibling tools like generate_ads_txt and the various list_* tools, so an agent can immediately tell what this tool does.

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 implies usage by identifying the report generation purpose, but it does not explicitly state when to choose this tool over alternatives or list any exclusions. An agent would infer from the word 'report', but there is no direct guidance such as 'use this to aggregate earnings data' or 'for account-level lists, use list_accounts instead.'

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