google_ads_list_conversion_actions

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

With no annotations, the description should disclose behavioral details. It only states it lists conversion actions but does not mention read-only nature, permissions, pagination, sorting, or rate limits. The docstring adds no behavioral context.

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?

Main description is a single clear sentence. The docstring is structured with Args, Returns, Example. However, some critical info (like parameter details) is missing from the main description, making it less effective.

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 3 parameters and an output schema, the description should explain what the tool returns and how parameters affect results. It doesn't mention default behavior of include_removed (false) or response_format. The example is minimal.

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?

The schema has 0% description coverage, so the description must explain parameters. It merely lists parameter names without explaining their meaning or behavior (e.g., include_removed, response_format). The example only shows customer_id.

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 'List all conversion actions in the account' clearly states the verb (list), resource (conversion actions), and scope (in the account). This distinguishes it from sibling tools like get_conversion_performance or create_conversion_action.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context for selecting this tool over other list tools such as google_ads_list_accounts.

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