yd_bid_modifiers_add

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'Add' but does not mention side effects, auth requirements, rate limits, or behavior when modifiers already exist. This is a significant gap for a mutation tool.

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 of 11 words, efficiently conveying the tool's purpose. It is concise but could benefit from slightly more detail without becoming verbose.

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 8 parameters, no annotations, and no output schema, the description is too brief. It fails to explain key aspects like the relationship between campaign_id and ad_group_id, or the meaning of numeric ranges in the schema. The context is incomplete for correct invocation.

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%, and the schema includes descriptions for each parameter. The description adds minimal value beyond naming categories (e.g., demographics, devices), so a 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 'Add bid modifiers (adjustments) for demographics, devices, regions, etc.' provides a specific verb ('Add') and resource ('bid modifiers'), and lists categories, clearly distinguishing it from sibling tools like delete, get, set, and toggle.

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 implies usage for adding modifiers but does not provide explicit guidance on when to use this tool versus alternatives like yd_bid_modifiers_set or yd_bid_modifiers_toggle. No exclusions or prerequisites are mentioned.

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