yd_keywords_get

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

With no annotations, the description must fully disclose behavior. It says 'Get keywords' implying a read operation, but fails to state whether it is read-only, requires special authentication, or has any side effects. No mention of rate limits or data scope.

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 a single sentence, which is concise, but it omits critical details that would justify further length. It is not structured to highlight key information upfront.

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 low schema coverage, no output schema, and no annotations, the description is insufficient. It does not explain how to use the optional parameters, what the response format is, or any constraints. A more complete description is expected for a 4-parameter 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?

Only 25% of schema parameters have descriptions (client_login). The three main ID parameters (campaign_ids, ad_group_ids, keyword_ids) lack any explanation beyond their names. The description does not clarify how these parameters interact (e.g., OR vs AND logic).

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 the tool retrieves keywords based on campaign, ad group, or keyword IDs. It identifies the verb ('Get') and the resource ('keywords'), differentiating it from sibling tools like yd_keywords_add or yd_keywords_bids_get. However, it does not specify what keyword attributes are returned.

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 provides no guidance on when to use this tool versus alternatives, such as yd_keyword_bids_get for bid-specific data. No mention of prerequisites, or when not to use it.

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