ad_manager_google_search_targeting

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description has a lower burden. However, it adds no behavioral context—it does not state what the tool returns (e.g., a list of targeting options) or any other operational detail. It doesn't contradict annotations, but fails to provide useful transparency beyond them.

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 a single short noun phrase, which is technically concise but severely under-specified. It lacks a verb, any qualifying detail, or structured information. A proper concise description would combine an action and object (e.g., 'Retrieves Google Ads search targeting options'), but this merely restates the tool's name.

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 no output schema, the description is the only source of information about what the tool returns. It fails to describe the return value, the meaning of the required 'type' parameter, or any other context. An agent could not correctly call this tool without substantial external documentation.

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 each parameter has a basic description. The tool description itself does not elaborate on parameters or their relationships, relying entirely on the schema. This meets the baseline for high coverage but adds no additional semantic 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 'Search targeting options' lacks a verb, making it ambiguous whether the tool retrieves, lists, or searches for targeting options. The name implies Google search targeting, but without an explicit action, an agent cannot clearly distinguish this from similar tools like ad_manager_fb_search_targeting or ad_manager_li_search_targeting.

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 is provided on when to use this tool, when not to use it, or how it differs from alternatives. The description does not mention that it's for Google Ads or that it should be used to fetch targeting options. The agent would have to infer usage from the name alone, which is insufficient.

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