suggest_keywords

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

With no annotations, description carries full burden and discloses paid API call, requiring user notification. This is a key behavioral trait. Lacks details on rate limits or authentication, but the warning is significant and adds value.

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?

Three succinct sentences with clear structure: purpose, important warning, usage advice. No extraneous information, front-loaded with core functionality.

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?

Despite no output schema, description sufficiently explains return data (related keywords with search volume and competition). For a tool with 6 parameters (1 required), the description covers key aspects. Could briefly mention limit behavior or pagination, but overall complete for use.

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%, but description adds value by specifying default locale ('en'), default location_code (2840 for US) with examples for Canada and UK, and noting domain uses SEO_CLIENT_DOMAIN if omitted. This enriches understanding beyond schema.

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?

Description clearly states the tool gets related keyword suggestions for a seed keyword using DataForSEO, with details on return data (up to 50 keywords, search volume, competition). It distinguishes itself from sibling like lookup_keywords by focusing on suggestion expansion.

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?

Provides clear guidance on when to use for expanding keyword research and finding related terms. Includes explicit instruction to inform user before calling due to paid API. Could improve by contrasting with alternatives like lookup_keywords, but usage context is well defined.

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