List Conversion Actions

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

readOnlyHint=true already establishes that this is a safe read. The description adds that the result conveys optimization primacy, which is useful framing, but the enumerated fields largely restate what the output schema already defines and it says nothing about pagination, result volume, or account-scope constraints beyond record count.

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?

Two short sentences, with the what (fields returned) front-loaded and the why (Smart Bidding check) second. No filler, though the field enumeration is slightly verbose without adding much beyond the output schema.

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 an output schema present, return-value detail is not required, and the description covers purpose, contents, and usage intent for a simple single-parameter read. It is complete enough to call correctly, missing only pagination/volume expectations.

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?

Only one parameter (customer_id) with 100% schema description coverage, so the schema fully documents it. The description adds no syntax, format, or ID-source guidance beyond what the schema provides; baseline 3 applies.

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?

States a specific verb (Lists) and resource (conversion actions) and enumerates what is returned: category, type, status, and primary_for_goal. An agent can distinguish it from write siblings like set_conversion_action_primary or set_campaign_conversion_goals at a glance.

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 second sentence gives a concrete usage context — checking what Smart Bidding optimizes toward, e.g. whether phone calls are primary. It does not name an explicit alternative or a when-not-to-use condition, so it stops short of a 5.

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