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 declares the tool is 'Read-only', notes it returns null when no match, and explicitly states what it does NOT return (value settings, lookback-window). Well below a 5 because it omits details like error handling or rate limits, but for a simple fetcher this is sufficient.

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 a single paragraph, but it efficiently covers purpose, return format, limitations, and sibling pointers without redundancy. Could be slightly more structured (e.g., bullet points), but every sentence earns its place.

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?

With no output schema, description gives return shape (id, name, type, status, category) and null result. Also mentions what is excluded. Does not specify error cases, but for a read-only fetch with clear ID parameter, it is fairly complete.

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%, but description adds value beyond schema: explains customer_id optionality with fallback to credentials, and sources conversion_action_id from list tool. This provides context that the schema alone does not.

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 'Fetch one conversion action's configuration from Google Ads by numeric ID'—specific verb, resource, and identifier. Explicitly distinguishes from sibling tools: mentions google_ads_conversions_tag for snippet 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 states when to use (fetch one conversion by ID), when not to (for value settings and lookback-window—use UI), and provides alternative tools (tag for snippet, list for full listing).

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