set_keyword_bids

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

With no annotations, the description discloses bulk adjustment, dry-run capability, and the micros unit via a prominent money note. However, it does not detail error handling, idempotency, or prerequisites like authentication.

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 front-loaded with purpose and usage guidance. The args list and money note are clear, though slightly verbose; overall concise with no wasted words.

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?

While parameter semantics are covered, the output is not described (e.g., success/failure indicators). Lacks mention of rate limits or prerequisites, leaving some gaps for a bulk operation 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?

Despite 0% schema coverage, the description fully specifies each bid object field (KeywordId required, SearchBid and NetworkBid in micros) and the confirm parameter, adding critical meaning absent from the 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?

The description clearly states 'Set search and/or network bids for keywords (bulk bid adjustment).' It uses a specific verb and resource, and distinguishes from sibling tool 'update_keywords' by noting it is more efficient for bid changes.

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 advises 'Prefer this over update_keywords when you only need to change bids — it uses the dedicated bids service and is more efficient.' It also explains the confirm parameter's role in executing vs. dry-run planning.

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