serp_adjacency_expand

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral details: graceful degradation without a DataForSEO key, and the autocomplete endpoint being undocumented and subject to change. No contradictions.

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 concise with 5 sentences, each adding essential information. It is front-loaded with the main purpose and well-structured, with no redundant or unnecessary words.

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?

Given the tool's simplicity (2 parameters, no output schema), the description fully explains what it does, how to use it, what it returns (per-seed suggestions + net-new terms), and its limitations. No gaps remain.

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 100% with descriptions for both parameters. The description adds meaning beyond the schema by specifying that 'seeds' should come from gsc_top_queries and that 'include_paa' defaults to true when DataForSEO is set. This helps the agent choose appropriate values.

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 clearly states the verb 'Expand' and the resource 'seed terms into adjacent terms from SERP signals'. It distinguishes from sibling tools like gsc_keyword_expand by specifying SERP signals (Google Autocomplete, PAA, related searches) rather than GSC data.

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 description gives clear usage guidance: pass winning queries as seeds (seed from gsc_top_queries), notes the free core and optional DataForSEO features, and explains graceful degradation. It does not explicitly state when not to use it or list alternative tools, but the context is clear.

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