google_ads_conversions_get

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

No annotations are provided, so the description carries the full burden. It discloses read-only nature, return shape (id, name, type, status, category), null-when-no-match behavior, and limitations (excludes value settings/lookback-window). This is highly transparent.

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 compact yet information-dense, front-loaded with the primary purpose, followed by return details, limitations, and alternatives. Every sentence contributes unique value.

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?

For a simple get-by-ID tool, the description covers return values, null case, exclusions, and sibling alternatives. Without an output schema, it sufficiently explains expected results.

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%; both parameters have detailed descriptions in the schema. The description adds only minor reinforcement ('by numeric ID'), so it doesn't exceed the baseline for well-documented schemas.

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 opens with a specific verb+resource+scope: 'Fetch one conversion action's configuration from Google Ads by numeric ID.' It clearly distinguishes from siblings by naming google_ads_conversions_list for full listings and google_ads_conversions_tag for tag snippets.

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 when to use alternatives: 'use google_ads_conversions_tag' for embed snippets, 'use google_ads_conversions_list' for full listings, and 'use the Google Ads UI' for value settings/lookback-window values. This provides clear when-not guidance.

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