ads_get_keyword_ideas

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only intent via 'Gets', but does not disclose output format, authentication requirements, rate limits, seed-selection behavior, or how errors are handled.

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 front-loaded sentence with no filler. It is appropriately concise, but given the tool's parameter complexity, slightly more structured context would have been beneficial.

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 tool has six parameters, nested objects, no output schema, and no annotations. The description only conveys the high-level purpose and leaves out important contextual details such as seed selection rules, return value shape, and pagination behavior, making it incomplete for reliable invocation.

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 coverage is 50%, and the description adds some useful context by linking 'seed keywords or URL' to the keywordSeed and urlSeed parameters. However, it does not clarify whether one seed is required, whether both may be supplied, or what pageSize semantics are beyond the schema's min/max.

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 (gets keyword suggestions) and the inputs ('based on seed keywords or URL'). It is clear enough to identify what the tool does, though it does not explicitly distinguish it from sibling tools like ads_list_keywords or ads_add_keywords.

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 given about when to use this tool versus alternatives, such as ads_list_keywords for existing keywords or ads_add_keywords for adding keywords. The intended use case is implied by the name but not explicitly stated.

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