Get keywords with performance

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns match type, status, and performance metrics and supports optional filters, but it does not mention default behavior, pagination, or side effects. As a read-only listing operation, some transparency is present but lacks detail on default scope or limits.

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 that front-loads the main action and includes the key optional filters and returned fields. No unnecessary words or repetition.

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?

For a tool with no output schema, the description communicates that the result is a list of keyword criteria with specific attributes. It provides essential usage context (optional filters) and return indications, though it omits details like default result limits and status-as-filter, which are visible in the schema.

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 schema only provides descriptions for half of the parameters, so the description's mention of filtering by ad group or campaign directly adds meaning to adGroupId and campaignId. However, it does not explain the limit parameter or that status can also be used as a filter, leaving some parameter semantics implicit despite partial compensation.

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 uses a specific verb 'list' and the resource 'keyword criteria', clarifying it returns keyword data with match type, status, and performance metrics. It clearly distinguishes from sibling tools like get_campaigns and get_search_terms by targeting keywords specifically.

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 states that results can be optionally filtered to one ad group or campaign, which tells the agent when to use this tool for keyword-level data. It does not explicitly name alternatives or exclusions, but the filter options provide clear context for typical use cases.

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