google_ads_conversions_get

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

With no annotations provided, the description fully discloses the behavior: it is read-only, returns specific fields or null when not found, and explicitly states what it does NOT return (value settings, lookback-window values). This sets proper expectations for the agent.

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 concise at three sentences, with the first sentence front-loading the purpose and return shape. Every sentence adds value: purpose, limitations, and sibling guidance. No redundant or filler content.

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 tool's simplicity (2 parameters, no output schema), the description covers all necessary aspects: what it does, what it returns, what it does not return, and how to access the data (including alternative tools). It is complete for an agent to understand and use correctly.

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 baseline is 3. The description adds minimal additional meaning: it mentions that customer_id is optional and falls back to credentials, and that conversion_action_id can be obtained via google_ads_conversions_list. While useful, it does not significantly enhance the schema's own parameter 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 'Fetch' and the resource 'one conversion action's configuration'. It distinguishes from siblings by explicitly mentioning google_ads_conversions_tag for tag snippets and google_ads_conversions_list for full listings, making its unique purpose unambiguous.

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 explicitly states when to use (to fetch a single conversion action by numeric ID) and when not to use (for value settings/lookback values, use the UI; for tag snippets use google_ads_conversions_tag; for listings use google_ads_conversions_list). This provides clear usage context and alternative tools.

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