google_serp

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

Goes beyond the annotations by disclosing that the sandbox returns dummy data with no payment (implying a billable production call) and by warning that titles/descriptions are untrusted third-party content. The prompt-injection warning is exactly the kind of behavioral context annotations cannot express.

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?

Front-loads what the tool returns, then the return shape, then environment and safety caveats. Every sentence carries information, though the returns list is slightly compressed into an otherwise dense block.

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 no output schema, the description usefully names the return fields (keyword, total_results_estimate, results) and discloses the sandbox behavior and content-trust caveat. It does not state whether production calls incur charges or whether result count is configurable, which is a minor remaining gap.

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%, so keyword, language_code, and location_code are already fully documented, including defaults and the no-search-operators rule. The description adds only the fixed 'top 10' scope, so baseline 3 applies.

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?

States a specific verb and resource ('Top 10 organic Google results ... for a keyword, desktop') plus the underlying provider (DataForSEO SERP Google Organic Live). This makes it immediately distinguishable from siblings such as bing_serp, news_search, and image_search.

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 'desktop' qualifier and the provider name imply this is the Google-web-results option versus bing_serp or news_search, but no explicit when-to-use or when-not-to-use guidance is given. The sandbox note adds environment context but not selection criteria.

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