ghl_ad_google_conversion_upsert

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict them. It adds endpoint details and OAuth scopes but does not elaborate on upsert behavior (e.g., what happens on conflict, required prerequisites like locationId). The additional context is minimal.

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 short and front-loads the purpose ('Upsert conversion'), followed by technical details (endpoint, OAuth). It is efficient but could be streamlined into a single coherent sentence. No wasted words.

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 no output schema and well-defined parameters in the schema, the description lacks mention of return values or behavior on duplicates. It also does not clarify that the conversion must belong to a location (though locationId is a required parameter). Overall, it is adequate for a simple mutation tool with good annotations.

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% with detailed parameter descriptions. The description adds no extra meaning beyond what the schema provides. Baseline 3 applies as the schema carries the burden.

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 clearly states 'Upsert conversion' and 'Create or update a Google Ads conversion action,' specifying the verb and resource. It distinguishes from siblings like get, delete, list, and goal_list, making the purpose unambiguous.

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 alternative conversion tools (e.g., ghl_ad_google_conversion_get, ghl_ad_google_conversion_list). It lacks explicit context on when to choose upsert over other operations, leaving the agent to infer from the name alone.

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