kadam_adv_update_site_bids

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

The description explicitly states idempotency, reinforcing the annotation, and explains the three allowed bid formats. It adds value beyond annotations by detailing the meaning of multipliers and the effect of '0'. However, it omits potential errors or authorization requirements.

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 concise (three sentences) and front-loaded with the core purpose. Every sentence adds value: purpose, bid format details, and idempotency note. No redundant or extraneous content.

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 tool with three string parameters and no output schema, the description covers the essential behavior (what it does, how to set bids, idempotency). It adequately contextualizes the tool without needing further details.

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 input schema already describes the parameters with high coverage. The description adds crucial context on bid syntax (number, multiplier, '0'), which clarifies valid values beyond the generic schema description.

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 specifies 'Set per-site (zone) bids for campaigns', clearly stating the action (set), resource (per-site bids), and scope (for campaigns). It distinguishes from siblings like 'kadam_adv_update_campaign_bid' by focusing on per-site 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?

The description explains how to format bids but does not provide guidance on when to use this tool versus alternatives like 'kadam_adv_bulk_update_bids' or 'kadam_adv_update_campaign_bid'. Usage context is implied but not explicit.

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