google_ads_conversions_get

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

No annotations provided, so description carries full burden. Clearly states read-only nature, what it does NOT return (value settings, lookback window), and fallback behavior for customer_id. Could be improved by mentioning rate limits or auth requirements, but current level is strong.

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 efficient and front-loaded. First sentence conveys purpose and return shape. Second sentence covers limitations, alternatives, and fallback. Every sentence adds value with no redundancy.

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 no output schema, description compensates by detailing return shape. Also explains fallback, omissions, and sibling tool distinctions. Fully informs an AI agent for correct selection and invocation.

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 baseline is 3. Description adds context: customer_id can fallback to environment variables, conversion_action_id is numeric and obtainable from list. Also describes return structure, which adds meaning beyond schema.

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 the tool fetches a single conversion action configuration by numeric ID. Specifies the return shape and includes null case. Differentiates from sibling tools by naming google_ads_conversions_tag for tag snippets and google_ads_conversions_list for full listings.

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 says to use this tool when fetching a single conversion action config by ID. States alternatives: use the UI for value settings and lookback window, google_ads_conversions_tag for HTML/JS tag, and google_ads_conversions_list for full listings. Provides clear context for 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.