google_ads_set_ad_schedule_bid_adjustments

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

No annotations provided; description only states 'Set bid adjustments' and mentions return as success message. Does not disclose if it overwrites existing schedules, requires permissions, or has side effects (e.g., destructive). Lacks behavioral details beyond basic operation.

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?

Well-structured: concise intro, bulleted args, return description, and comprehensive example. Every sentence adds value; no redundancy.

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?

Output schema exists, so return value minimal description is acceptable. Covers purpose, usage context, and all parameters clearly. Lacks explicit prerequisites (e.g., customer/campaign must exist) but is otherwise complete.

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 description fully compensates. It details each parameter: customer_id format (no hyphens), schedules sub-fields with allowed values (day_of_week, hours/minutes ranges, bid modifier 0.1-10.0), and example values. Adds meaning beyond schema's generic types.

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 it sets bid adjustments for ad scheduling (dayparting), with verbs 'Set bid adjustments' and 'Control when your ads show'. It distinguishes from siblings like 'set_device_bid_adjustments' or 'list_bid_adjustments' by focusing on time/day adjustments.

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?

It provides context (useful for targeting business hours, weekends) but lacks explicit guidance on when to use versus alternatives like 'set_campaign_schedule' or 'set_device_bid_adjustments'. No when-not-to-use or exclusion criteria.

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