Search TOP results

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

The description adds the useful behavioral warning that the operation may consume SEO Intellect account limits, which is not present in annotations. However, it does not disclose the asynchronous task_id/wait_for_result behavior, polling, or timeout semantics, which are significant for a non-read-only operation.

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 short and front-loaded with the main purpose. The 'Upstream API tool: top-10' sentence adds some technical context but is somewhat redundant with the tool name; overall it remains concise and readable.

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 has a complex schema with two invocation modes, async behavior, polling, and timeout parameters, but no output schema. The description does not explain the task_id continuation flow, when to wait vs. poll, or what the result shape looks like, leaving important operational context missing.

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 high and several parameters already have descriptions. The description only adds that keywords are supplied, which is minimal extra meaning beyond the schema. It does not explain the two invocation branches (new task vs. existing task_id) or parameters like se, region, and depth.

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 action ('Export search results') and the core input ('supplied keywords'). The title 'Search TOP results' and tool name 'top_10' clarify that this targets top search results, though the description does not explicitly distinguish it from sibling search-related 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 is provided about when to choose this tool over siblings like positions, relevant_pages, or suggest. The only additional operational note is that it may consume account limits, but there is no when-to-use or when-not-to-use guidance.

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