Get search terms report

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

In the absence of annotations, the description relies on the verb 'List' to signal a read-only report operation. However, it does not disclose any potential caveats such as result limits, ordering, or permission requirements beyond what is implicitly suggested.

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 succinct sentences that front-load the core purpose and then add a practical use case, with no redundant 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 tool has no output schema and no annotations, and the description gives only a broad 'performance metrics' without specifying which metrics are returned or how the optional parameters affect results, leaving some ambiguity for an agent.

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 describes campaignId but not limit or dateRange, and the description does not elaborate on any parameter semantics. With only 33% schema description coverage, the description should compensate but does not.

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 the tool 'list[s] the actual search terms that triggered your ads, with performance metrics,' which clearly identifies the resource (search terms) and the action (list with metrics), distinguishing it from sibling tools like get_keywords or search_gaql.

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 phrase 'Useful for finding negative keyword candidates' provides a specific use case, but it does not mention when not to use the tool or name alternative tools for other scenarios.

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