google_ads_add_price_extension

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

With no annotations, the description should fully disclose behavior. It explains the operation and some parameter constraints (e.g., items count 3-8, qualifier values) but does not mention whether the operation is destructive, reversible, or what the return result contains beyond a vague statement. Key behavioral aspects are missing.

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 sections for intro, args, schema, returns, and example. It is concise yet comprehensive, with no unnecessary words. Each section earns its place.

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 existence of an output schema, the description need not detail return values. It covers parameter constraints and provides an example. However, it could include more context about prerequisites (e.g., campaign must exist) and potential errors, though the output schema may cover some of that.

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 0%, so the description carries the full burden. It provides detailed meaning for each parameter: customer_id format (10 digits, no hyphens), campaign_id, price_qualifier with enum values, and items_json with a JSON schema and count constraint (3-8 items). An example further clarifies usage.

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 the tool adds a price extension to a campaign and explains what price extensions are, distinguishing it from sibling tools like add_call_extension or add_promotion_extension. The verb 'Add' and resource 'price extension' are specific.

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 does not explicitly state when to use this tool versus alternatives or when not to use it. The implied usage is clear (when adding a price extension), but no exclusions or comparisons are provided, leaving the agent to infer from sibling names.

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