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

Annotations supply a safety profile (though destructiveHint=true is odd for a read query), so the bar is lower. The description adds what data is returned but omits the operationally critical behavior: the 1000-result cap, pagination via offset_token, and that requesting >10,000 results requires it. It never contradicts the annotations, but it leaves the pagination model undisclosed.

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?

Two sentences, front-loaded with the endpoint name, but the 'over 7 billion keywords' figure is promotional padding that consumes space without helping an agent call the tool.

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?

An output schema exists so return-shape explanation is unnecessary, but the description omits usage context, scope selection, and pagination constraints for a live data endpoint that can be called in several ways. Given the complexity of the body schema, the description is under-specified.

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?

Top-level schema description coverage is 0% and the description offers no parameter guidance at all — not location/language requirements, not limit/offset behavior, not the offset_token precedence rule. Although the nested body schema is detailed, the description fails to compensate for the undocumented top-level parameter.

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 identifies the endpoint and that it returns keywords with Google Ads metrics, product categories, and SERP data, but it is phrased as marketing copy ('can provide you with over 7 billion keywords') and never states what a 'top search' actually is or how scope (location/language) defines the result. It is distinguishable from Bing/GAds siblings only by the DataForSEO Labs branding, not by an explicit contrast.

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?

There is no when-to-use guidance and no alternatives named, despite many sibling keyword tools (keyword_ideas, keyword_suggestions, related_keywords, gads_kw_for_keywords). The agent gets no signal for choosing this endpoint over a near-identical sibling.

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