ghl_ad_google_audience_get

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by specifying the exact endpoint, API version, and OAuth scope (adPublishing.readonly), which are not in annotations and provide key 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?

The description is very concise: a title, a one-sentence action, and technical details (endpoint, version, OAuth). Every sentence is necessary and front-loaded. No fluff.

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 the simple read-only nature, good annotations, and no output schema, the description is largely sufficient. It includes endpoint and auth scope. Minor gap: it doesn't explicitly state that it returns the full audience object, but that is implied.

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 baseline is 3. The description does not add any parameter-specific meaning beyond the schema; it only mentions 'by ID' which is already in the schema. No extra value.

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 'Get audience by ID' and 'Retrieve a specific Google Ads combined audience by ID', using a specific verb and resource. It distinguishes itself from siblings like list (returns many) and upsert (creates/updates) by focusing on retrieval by ID.

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 implies usage when you have an audience ID and need a single audience, but it lacks explicit guidance on when not to use this tool or mention of alternatives like list or upsert. No exclusions or context are provided.

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