discover_keywords

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

With no annotations, the description bears the burden of behavioral disclosure. It explicitly states the operation is non-mutating ('nothing is created in the account') and that results are bounded by row limits with pagination tokens. This adds meaningful behavioral context beyond the input schema.

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 two sentences and front-loaded with the core purpose, followed by side-effect and pagination context. Every sentence earns its place without redundancy or filler.

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?

The description covers the main behavior, non-mutation, and pagination, but it does not mention the customer_id parameter or clarify whether at least one of seed_keywords or page_url is needed. Given the lack of an output schema and no annotations, an agent has a moderate but not complete picture.

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 maps seed_keywords to 'seed terms', page_url to 'page URL', and page_token to 'pagination tokens', but it does not mention customer_id at all. It adds partial value but leaves one parameter unexplained.

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 a specific action: generating keyword ideas from seed terms and/or a page URL, with average monthly searches and competition. It clearly identifies the resource and purpose, though it does not explicitly differentiate this from siblings like get_keyword_forecasts.

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 gives clear context for when to use the tool: when keyword ideas are needed from seed terms or a page URL. It does not name alternatives or exclusions, but the usage scenario is concrete enough to guide selection.

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