Longtail Keywords

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

No annotations provided, and the description only states 'Fetch longtail (low search volume) keywords' without disclosing behavioral traits such as pagination, rate limits, or what happens if no results are found. The endpoint is mentioned but adds minimal transparency.

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?

Description is very short (one sentence), achieving conciseness, but it lacks structure such as sections or bullet points. It could be more informative without being overly verbose.

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 19 parameters, no output schema, and no annotations, the description is too brief. It does not explain return values, pagination, or filter behavior, leaving the agent without sufficient context for correct invocation.

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% (all 19 parameters have descriptions), so the description does not need to add much. The description itself adds no parameter-specific meaning; baseline 3 is appropriate.

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 it fetches longtail keywords with low search volume, and the name 'keywordsLongtail' aligns with sibling tools like 'keywordsRelated' and 'keywordsSimilar', providing some differentiation. However, it could more explicitly contrast with similar keyword tools.

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?

No guidance on when to use this tool vs alternatives (e.g., keywordsRelated or keywordsSimilar). The description does not mention prerequisites, when not to use it, or preferred use cases.

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