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

Annotations already cover safety (readOnly, non-destructive, openWorld), so the description's added value is the cost/latency profile: 'one billable DataForSEO request with a depth of 10.' That is genuinely useful context beyond the structured fields. It omits rate limits or failure behavior, and idempotentHint=false is not explained (repeat calls are re-billed).

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 short sentences, zero filler, with the usage trigger front-loaded before the cost note. Every clause earns its place.

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 need not detail return values, and the depth-of-10 note implicitly signals ~10 organic results. Annotations carry the safety profile. The only gap is that language/location selection (important for SERP correctness) is left entirely to the schema.

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 67%: languageCode and locationCode are documented in the schema, but the required 'keyword' param carries only length constraints. The description adds 'for a keyword' but no format or syntax guidance, and its mention of 'depth of 10' refers to a setting that is not even a parameter, which could confuse an agent looking for a depth input. Baseline 3 is appropriate since the schema does most of 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?

The description names a specific verb (get) and resource (live Google SERP) for a given keyword, matching the title and distinguishing it from sibling DataForSEO tools like dataforseo_backlink_summary and dataforseo_ranked_keywords. It is clear what the tool returns, though it does not explicitly contrast itself with the other SERP/search siblings.

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?

It gives an explicit trigger: 'Use this when a team member asks for current Google search results for a keyword.' That is clear contextual guidance. It stops short of naming alternatives or exclusions (e.g., when to prefer a cached/history SERP tool instead), so it is not a full 5.

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