SERP overview

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

With no annotations, the description carries the burden of behavioral disclosure. It honestly describes the output fields (domain rating, URL rating, traffic, page type, result type) but does not reveal behaviors like pagination, number of results limit (top_positions), response format, or potential external network calls. It is a read-only operation implied by the description, but lacks richer context.

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 a single, front-loaded sentence that efficiently lists the core purpose and key output fields without unnecessary words. It is concise and well-structured.

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?

The tool is relatively simple with 3 parameters and no output schema, so the description gives a reasonable overview of the return fields. However, it lacks details on top_positions behavior, country effects, or the structure of the returned data, which is important in absence of an output 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 description coverage is only 33% (only country has description). The description adds some meaning by referring to 'keyword' and 'top search results', but it does not explicitly explain the top_positions parameter or how the output is affected by it. It does not compensate for the low coverage.

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 tool returns 'Top search results for a keyword' with specific metrics (domain rating, URL rating, traffic, page type, result type). This is a specific verb+resource+scope that distinguishes it from sibling tools like keyword-volume-history or organic-keywords.

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 implies usage (for seeing SERP results with metrics) but provides no explicit when-to-use guidance or mentions alternatives. It does not say when not to use this tool versus siblings like organic-keywords or domain-rating.

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