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

Goes well beyond the readOnly/idempotent/openWorld annotations: it discloses cost (FREE, non-billable sources), rate limiting driven by three upstream calls, the absence of a keyword-to-URL index, and precise semantics for coverage.serpUnavailable/suggestionsUnavailable (source unreachable vs. genuinely empty, partial failure tolerated). This is exactly the kind of operational context annotations cannot carry.

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?

Front-loads the one-line purpose before any caveats, and each following sentence adds a distinct operational fact (free, rate limit, no URL index, coverage semantics, ungrouped retention). It is dense but slightly long, with a couple of clauses that could be tightened.

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?

No output schema exists, so the description carries the return-shape burden and does: it explains the clusters grouping, the ungrouped bucket, and the coverage flags that signal partial failures. Combined with the cost and rate-limit notes, an agent has everything needed to call and interpret this tool correctly.

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 100%, so keyword, projectId, languageCode, and locationCode are already documented with defaults and constraints. The description adds nothing about parameter formats or interactions, which is the expected baseline when the schema does the work.

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?

Names the specific resource (content ideas / topic research for a seed keyword) and spells out what composes it: SERP titles, PAA-style questions, and autocomplete suggestions clustered by shared phrasing. It clearly separates itself from adjacent siblings like research_keywords, get_keyword_serp_overview, and the saved-keyword Topic Clusters feature.

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?

Gives strong context for when to reach for it — free sources, three upstream calls, rate limited — and explicitly says what it is NOT (a keyword-to-URL overlap report). It never names a concrete sibling to use instead when the agent wants overlap data or broader keyword research, so the alternative routing is implied rather than explicit.

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