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

Very strong: it discloses quota consumption (once per request against keyword_lookups_per_day), a bounded number of AI-gateway brief calls, and the exact semantics of briefSkipped (honest 'not attempted' vs empty brief) and page.status (text-match, never a verified ranking). This goes well beyond the annotations; the readOnlyHint=false and non-idempotent annotations are consistent with the quota/AI side effects it describes.

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-loaded with the pipeline definition, and most sentences carry genuine semantic weight (quota, AI budget, briefSkipped, page.status). It is dense and long, with some clauses that could be trimmed, but it is not padded.

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?

With no output schema, the description does the work of explaining the return shape (clusters, page.status, brief/briefSkipped), which is the critical part for an agent to interpret results. It doesn't enumerate the full response structure, but the semantically important fields are covered.

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 the schema already documents all four parameters (keywords range, projectId, languageCode, locationCode). The description adds pipeline context but no parameter-level meaning beyond the schema's own descriptions, so the baseline of 3 applies.

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?

States a specific verb+resource and the exact transformation pipeline: 'a volume -> cluster -> page -> brief pipeline over 1-500 pasted keywords'. It explicitly distinguishes itself from siblings by naming the shared components it reuses (bulk keyword lookup, the Topic Clusters clustering engine, get_topic_research), so an agent can tell it apart without opening the schema.

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 role is implied (a full strategy pipeline over a pasted keyword list), and it references related tools/features, but it never states plainly when to choose this over get_topic_research or research_keywords, nor any exclusion condition. Usage context is inferable but no explicit routing guidance is given.

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