google_ads_device_targeting_get

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

No annotations provided, so description carries full burden. It details output shape, semantics of enabled=False, bid_modifier=0.0 meaning delivery off, and explains mureo's convention. Fully discloses behavioral traits.

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 appropriately sized, front-loaded with purpose, then details. Every sentence provides value, though slightly longer than necessary. Efficiently 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?

No output schema, but description compensates by fully describing the return structure and semantics. Also ties to sibling tools for modification. Comprehensive for a read-only retrieval tool.

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 100% description coverage for both parameters. Description does not add significant new meaning beyond what is already in schema; it reiterates the fallback logic for customer_id which is already described.

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 clearly states it gets device targeting state for a Google Ads campaign, specifies return structure (always three entries in order), and distinguishes from sibling tools like google_ads_device_targeting_set and google_ads_bid_adjustments_update.

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 states it is read-only, explains when enabled defaults to True when no criterion exists, and directs to sibling tools for modification. Provides clear context on when to use and when not to use.

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