ad_manager_google_upsert_conversion

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the agent knows the operation is safe to retry and non-destructive. The description adds nothing about side effects, prerequisites, or what happens on update vs create. With annotations present, the bar is lower, but the description still provides no behavioral context beyond the annotations.

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 extremely short (two words), but this is under-specification rather than concise efficiency. It lacks essential detail and does not front-load useful information. It is not appropriately sized for the complexity of the tool.

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 9 parameters, a nested object, and no output schema, this description is completely inadequate. It does not explain what a conversion is in the Google Ads context, how the upsert behaves, or any prerequisites. The agent has to infer everything from the schema, which is insufficient for a complex write operation.

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 description coverage is 100%, and all parameters have descriptive text in the schema. The description adds no parameter-specific information, but since the schema fully documents parameters, a baseline 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?

The description "Upsert conversion" is a tautology that restates the tool name without adding any specific information. It does not specify what kind of conversion, which ad platform (Google), or how it differs from other upsert tools (e.g., ad_manager_fb_upsert_ad). An agent cannot distinguish this tool from many siblings based on this description.

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?

There is no guidance on when to use this tool versus alternatives. No mention of use cases, prerequisites, or exclusions. The description gives no context about when an agent should select this tool over others.

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