ghl_ad_google_segment_upsert

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

Annotations already indicate idempotent and non-destructive write behavior. The description adds value by specifying the exact endpoint and required OAuth scopes (adPublishing.write), which are not in annotations. This helps the agent understand authorization needs and the API contract.

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 concise (3 lines) and front-loaded with the purpose. However, it could be more structured (e.g., separate sections for purpose, endpoint, auth) to improve readability.

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?

For a complex tool with nested input schema (rule-based lists, members) and no output schema, the description is too minimal. It does not explain the overall segment structure or what the response contains, relying entirely on the schema.

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%, so the input schema already documents all parameters fully. The description adds no extra meaning beyond noting the body is from the OpenAPI spec; it does not explain complex nested structures like rule-based user lists or member types.

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 states 'Create or update a Google Ads audience segment' with a clear verb (upsert) and specific resource (Google Ads audience segment). It distinguishes from sibling tools like list, delete, get, and offline_job_create by focusing on the upsert operation.

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 versus alternatives such as ghl_ad_google_audience_upsert or other segment operations. The description does not mention when not to use it or provide context for switching between create and update behavior.

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