direct_get_keyword_bids

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

No annotations are provided, so the description carries the burden. 'READ' and the listed return types (SearchBid/ContextBid/AuctionBids) disclose the non-destructive nature and expected output. But it omits behaviors like pagination, limit semantics, or what happens with no filters.

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?

A single, front-loaded sentence with a clear READ prefix and no filler. All words earn their place, efficiently conveying method, resource, data types, and filter usage.

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 no output schema or annotations, the description covers the core purpose and filter inputs, but lacks details on default behavior (e.g., no filters), limit effects, and return format. It's adequate for a simple getter but not fully self-sufficient.

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 description coverage is only 25% (only 'project' has a description). The description mentions keyword_ids and campaign_ids/project but does not explain the 'limit' parameter or clarify the optionality semantics. It adds some value by indicating 'and/or' combination, but insufficiently compensates for the coverage gap.

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?

Description clearly states it's a READ operation for keyword bids (SearchBid/ContextBid/AuctionBids), with a specific resource. It distinguishes from sibling direct_set_keyword_bids by using 'READ' and naming the keywordbids.get method.

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?

Provides explicit guidance on which parameters to pass ('keyword_ids and/or campaign_ids/project'), which helps select and invoke. However, it doesn't state when to prefer this over alternatives like direct_list_keywords or direct_get_campaign, nor does it mention any exclusions or fallback behavior.

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