gold_keyword_serp_features

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

With no annotations, the description carries the behavioral disclosure burden. It usefully adds that no API key is required and that the tool is paid-only, and it explains that it performs live SERP HTML fetching and feature detection. It does not disclose output format, failure modes, or rate limits, so transparency is partial.

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 dense and includes important constraints like no API key and paid-only in a compact space. The 'POWER:' prefix is hype that adds no functional signal, which keeps it from a perfect score.

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?

There is no output schema, and the description never states what the tool actually returns, such as a list of detected features, booleans, or raw HTML. It also does not describe behavior when no features are present or when the keyword is invalid, leaving a meaningful gap for an agent that must interpret results.

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 0%, and the description only clarifies that 'keyword' is the search term. The lang and region parameters are left entirely to inference from their names and defaults, so the description does not compensate for the missing schema documentation.

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 action ('fetch Google SERP HTML for a keyword') and a concrete deliverable ('detect features present') with examples such as PAA box and featured snippet hint. This clearly differentiates it from sibling keyword tools like expansion or gap scanning.

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?

'So you know the fight before writing' gives an implied use case for pre-writing SERP reconnaissance. However, it does not explicitly say when to prefer this tool over siblings like gold_keyword_brief or gold_keyword_expand, nor does it state any exclusions.

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