yd_keyword_bids_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic function without mentioning whether it is read-only, any rate limits, authorization requirements, or what happens when no parameters are specified.

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 very concise, consisting of a single sentence. While it is front-loaded, it is arguably under-specified for a tool with multiple optional parameters and no output schema. A few more sentences could significantly improve usefulness without being verbose.

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 4 optional parameters, no output schema, and numerous sibling tools, the description is far from complete. It provides no information on return values, filtering logic, or how to effectively use the tool in context. The agent would need to guess or rely on external documentation.

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 description adds no information about the four input parameters. Schema description coverage is only 25% (only client_login has a description), and the tool description does not clarify the role of campaign_ids, ad_group_ids, or keyword_ids. The agent receives no guidance on how these parameters filter the results.

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 states 'Get keyword bids and traffic forecasts,' clearly identifying the verb (Get) and resource (keyword bids and traffic forecasts). However, it does not explicitly differentiate itself from sibling tools like yd_keywords_get or yd_bids_set, though the 'get' vs 'set' distinction is implicit.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions. The agent must infer usage from the name alone.

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