google_ads_extension_performance_report

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

No annotations are provided, so the description must fully convey behavioral traits. It fails to mention data freshness, pagination, rate limits, or any side effects. While 'Get' implies a read operation, the description lacks sufficient transparency 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: two sentences for purpose/benefit, then structured Args, Returns, and Example sections. No redundancy, and the most critical information is front-loaded.

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 that an output schema exists, the description is appropriately complete for a reporting tool. It covers all parameters adequately. However, it could mention the general structure of the returned report (e.g., columns like clicks, impressions) to enhance usability, though the output schema may provide this.

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 0%, but the description's Args section adds significant meaning: customer_id format (10 digits, no hyphens), campaign_id as optional filter, and date_range with explicit allowed values (LAST_7_DAYS, LAST_30_DAYS, LAST_90_DAYS). This compensates well for the schema's lack of descriptions.

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 verb 'Get' and the resource 'performance metrics for ad extensions', distinguishing it from sibling performance reports like account or campaign performance. The additional line about showing which extensions are performing well clarifies the tool's value.

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 for analyzing extension performance but does not explicitly state when to use it over alternatives, such as other performance reports or extension management tools. No exclusions or prerequisites are mentioned.

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