remove_ad_schedules

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

The description states a write operation ('Remove'), which aligns with the annotation 'readOnlyHint: false'. However, it does not disclose additional behavioral traits such as whether the removal is permanent, if it affects active campaigns, or any required permissions. The description is adequate but minimal.

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 sentence with no unnecessary words. It is front-loaded with the core action and specific detail, making it highly concise and efficient.

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 availability of an output schema, the description does not need to explain return values. The description covers the essential action and parameters. It could mention relationships with sibling tools (e.g., 'replace_ad_schedule') but remains reasonably complete for a straightforward deletion tool.

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 100% description coverage for both parameters. The description adds no extra meaning beyond what the schema already provides (e.g., 'criterion_ids' described as 'Campaign criterion ids (from get_ad_schedules)'). Thus, baseline score of 3 is appropriate.

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 verb 'Remove' and the resource 'ad-schedule (dayparting) windows', and specifies the method 'by criterion id'. This distinguishes it from sibling tools like 'add_ad_schedules' and 'replace_ad_schedule'.

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 versus alternatives like 'replace_ad_schedule'. The description lacks context such as prerequisites or scenarios where removal is preferred.

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