google_ads_ads_policy_details

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

Declares itself as 'Read-only', which is a key behavioral trait. Also describes the response contents in detail. Without annotations, the description adequately covers safety and output behavior, though it could mention required permissions.

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?

Single-paragraph description is concise and front-loaded with the main purpose. Could be slightly more structured, but it is efficient and contains no fluff.

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 covers the output fields and usage context well. No output schema; but the listed fields are sufficient. Could mention error handling or limits, but overall complete for the tool's simplicity.

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 100%, so the description adds no additional parameter meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Clearly states it fetches policy review results for a single ad, listing key outputs like approval_status and policy_topic_entries. Differentiates from siblings by specifying it follows google_ads_ads_list for non-APPROVED ads.

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?

Explicitly instructs when to use: after google_ads_ads_list surfaces a non-APPROVED ad. Provides clear context and a specific trigger, which helps an agent decide when to invoke this tool.

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