google_ads_add_structured_snippet

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

No annotations are provided, and the description does not disclose behavioral traits like request limits, authentication needs, or that the operation modifies the campaign. It only indicates creation without detailing side effects or restrictions.

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 well-structured with an Args section and an example, but it contains redundant explanations (e.g., repeating 'Structured snippets highlight...'). Still, it is efficient and front-loads the purpose.

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 presence of an output schema, return values are covered. The description adequately explains parameters and provides an example, but lacks details on error handling, prerequisites (e.g., campaign must exist), or limitations.

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?

The schema has 0% description coverage, so the description adds value by specifying customer_id format (10 digits, no hyphens), header options, and values_json constraints (3-10 items). However, campaign_id is not elaborated, and some parameters remain opaque.

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 "Add structured snippet extension to a campaign" with a specific verb and resource. It distinguishes from sibling tools like google_ads_add_callout_extension by focusing on structured snippets.

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 provides an example and lists common headers, offering implicit usage context. However, it does not explicitly state when to use this over alternative extensions or provide contraindications, so guidance is present but not comprehensive.

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