google_ads_schedule_targeting_update

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

No annotations provided, so description carries full burden. Discloses return format (list of resource_names), mutability, default start_minute/end_minute values, and reversibility method. Lacks error handling or permission details but covers key behaviors.

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?

Concise multi-sentence description front-loads purpose. No redundant information. Every sentence adds critical context.

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 complexity (mutation with add/remove), missing annotations, and no output schema, the description covers return format, defaults, and constraints. Could include atomicity or error states, but sufficient for typical use.

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 100%, but description adds value beyond schema: explains default behavior for start_hour/end_hour (ZERO), customer_id fallback, and the 'at least one' rule. Enhances understanding of parameter 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?

Clearly states the verb (add/remove), resource (ad-schedule criteria on a campaign), and action (single mutate). Distinguishes from sibling google_ads_schedule_targeting_list for read-only use.

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?

Specifies conditions: at least one of add_schedules/remove_criterion_ids must be provided. Notes reversibility via inverse operations and defaults for new schedules. Could mention when not to use, but sufficiently clear.

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