ghl_ad_google_asset_upsert

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

Annotations already indicate mutability (readOnlyHint false). Description adds useful behavioral context: the specific endpoint (POST /ad-publishing/google/assets) and required OAuth scope (adPublishing.write). No contradictions with 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?

Extremely concise: three lines covering title, purpose, endpoint, and scopes. No filler, front-loaded with key info.

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?

Adequate given rich schema and annotations. Lacks mention of asset types (CALL, SITELINK, LEAD_FORM) and dynamic payload shape, but schema covers that. No output schema, but description doesn't explain return value.

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%, so baseline is 3. Description does not add extra meaning beyond what the schema provides. The body parameter and its nested structure are fully defined in the schema.

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?

Clearly states the tool does an upsert of Google Ads creative assets, using specific verbs 'Create or update'. Distinguishes from sibling tools like list (ghl_ad_google_asset_list) and other upsert tools (ghl_ad_google_audience_upsert).

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?

No guidance on when to use this tool vs alternatives (e.g., when to use ghl_ad_google_asset_list instead). No scenarios or exclusions mentioned.

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