google_ads_get_bid_recommendations

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

With no annotations, the description must fully disclose behavior. It mentions Google's recommendation engine and possible recommendation types, but omits details like permissions, rate limits, or side effects (though read-only is implicit). The transparency is adequate but not thorough.

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 and well-structured, with a brief intro, bullet points of recommendation types, and clear sections for args, returns, and an example. No redundant information, though the returns section is minimal.

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 the tool has an output schema and only two parameters, the description covers the core functionality adequately. However, it lacks usage guidance and does not explain how it fits into workflows with sibling tools, which would enhance completeness.

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 0%, so the description must compensate. It explains customer_id format (no hyphens) and that campaign_id is optional, but does not elaborate on how campaign_id filters recommendations or provide examples of valid values beyond the basic example.

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 it retrieves AI-powered bid recommendations from Google Ads, listing specific types like keyword bid adjustments and campaign budget increases. This distinguishes it from sibling recommendation tools like get_recommendations, which are broader in scope.

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 implies usage for getting bid recommendations but lacks explicit guidance on when to use this tool versus alternatives (e.g., get_recommendations, apply_recommendation). No when-not or prerequisite conditions are provided.

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