google_ads_shopping_performance

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

No annotations exist, so the description must cover behavioral traits. It describes the tool as retrieving read-only metrics but lacks details on rate limits, authentication, or any side effects. It is a simple retrieval, but more transparency would be beneficial.

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?

Description is front-loaded with purpose, includes args and a clear example. While efficient, it could be slightly more concise without the example, but overall well-structured.

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 presence of an output schema, the description adequately explains the function. It covers all three parameters and gives a high-level return type. For a read tool with simple parameters, this is sufficient.

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?

Input schema has 0% description coverage, but the description adds valuable meaning: customer_id format (10 digits, no hyphens), campaign_id as optional, and date_range with example values. This compensates well for the schema gap.

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?

Description explicitly states 'Get performance metrics for Shopping campaigns' and highlights ROAS, clearly differentiating from other performance tools like google_ads_campaign_performance and google_ads_account_performance.

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?

Description indicates critical use for Shopping campaign optimization, providing clear context. However, it does not explicitly mention when not to use or list alternative tools for other campaign types.

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