google_ads_get_pmax_assets

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

No annotations are present, so the description carries the behavioral burden. It adds useful context by naming the source table and mentioning that date-range metrics are optional, but it does not disclose output shape, default date behavior, or whether only certain asset statuses are included. The read-only nature is implied by 'List'.

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?

One concise front-loaded sentence states the core action and resource first, then adds context and optional metrics. There is no filler or redundant wording; every phrase contributes meaning.

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?

The description captures the essential resource and optional metrics, but with 8 parameters, no output schema, and no annotations, it leaves the return value shape, metric fields, and differentiation from PMax diagnostic/placement tools underspecified. It is adequate for basic invocation but not fully complete for nuanced agent decision-making.

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 high (75%), so the schema already documents the main parameters including dates, fieldType, customerId, and campaign/asset group IDs. The description reinforces the date-range/performance metric connection but adds no substantial meaning beyond what the schema 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 ('List') and clearly scopes the resource to Performance Max asset group assets from asset_group_asset. It is distinguishable from PMax sibling tools like get_pmax_placements or get_pmax_asset_diagnostics, though it does not explicitly name those alternatives.

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 does not state when to use this tool versus siblings like get_pmax_asset_diagnostics, and provides no explicit exclusions or alternative routing. An agent must infer usage from the tool name and resource phrasing.

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