kadam_adv_update_campaign_bid

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

Adds info beyond idempotentHint: notes it's faster/safer, and the country limitation (no new countries). Not fully detailed on error cases but adequate.

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?

Three short, front-loaded sentences. No wasted words; each sentence adds distinct value.

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?

For a simple update with idempotentHint, covers key behavior; missing output schema is mitigated by simplicity. Could explain error handling but not critical.

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% with good descriptions. Description adds nuance for countries (default keep, only updates existing), which is valuable beyond schema.

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 it updates bid for a single campaign without full payload, and distinguishes from the sibling kadam_adv_update_campaign by highlighting speed and safety.

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?

Explicitly indicates when to use (only bid change needed) and what happens with countries; names the alternative tool. No explicit exclusion of bulk update but sufficient for most scenarios.

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