kadam_adv_bulk_update_bids

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

Annotations provide idempotentHint=true. The description adds critical behavioral details: mixing pricing models errors out and countries are required. It does not mention if updates overwrite existing bids (implied) or what the response looks like, but given minimal annotations, the description provides meaningful context beyond annotations.

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?

Two sentences, no filler, front-loaded with the core action. Every sentence provides necessary information without redundancy. Highly 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?

The description covers the main action and critical constraints (pricing model, countries). It doesn't explain return values (no output schema) or other edge cases, but for a 4-parameter bulk update tool with high schema coverage, it is sufficiently complete for agent decision-making.

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%, so each parameter is already documented. The description adds cross-parameter business logic: all campaigns must share one pricing model. This adds value beyond individual parameter descriptions, justifying a score above baseline 3.

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 'Set the same bid on multiple campaigns at once', with a specific verb and resource. It adds constraints (pricing model, countries) that distinguish it from sibling tools like kadam_adv_update_campaign_bid (single campaign) and kadam_adv_update_site_bids (site level).

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 explicitly states that all campaigns must share one pricing model and that countries are required. This provides clear context for when to use the tool. However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance, but the constraints serve as implicit guidance.

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