google_ads_conversions_list

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

Declares read-only and describes ordering and return structure. However, with no annotations provided, additional details about authentication or rate limits are missing. Still adequately informs about basic behavior.

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?

Extremely concise: two sentences plus a list of return fields. Front-loaded with the core purpose. Every sentence adds value and no redundant information.

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 simple tool (one optional parameter, no output schema), the description is complete. It details the return fields, provides usage context, directs to a sibling tool, and covers the single parameter's behavior. No gaps remain.

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 coverage is 100%, so the schema already documents the optional customer_id parameter. Description adds that it falls back to configured credentials when omitted, which is helpful but not extensive. Baseline score of 3 is appropriate.

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?

Explicitly states it lists every conversion action on the Google Ads customer, ordered by numeric id. Distinguishes from siblings by specifying the returned fields (id, name, type, status, category) and noting its use for discovering conversion_action_id before calling other tools like .get, .update, .remove, or .tag.

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?

Provides clear guidance: use this to discover conversion_action_id before calling get/update/remove/tag. Also directs to google_ads_conversions_performance for CV performance metrics, explicitly stating when not to use this tool.

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