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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own — no indication that this retrieves results of a previously submitted asynchronous task, or the 30-day retrieval window (that detail lives only in the schema).

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?

It is short, but vacuously so: the single sentence is filler that conveys no information and does not earn its place. This is under-specification posing as brevity, not genuine conciseness.

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?

An output schema exists, so return values need not be described, but the description still fails to say what the tool does or how it relates to the submit/live siblings. For a retrieval tool in a large family of near-identical names, that omission leaves the agent without the one thing it needs.

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 100% for the single 'id' parameter, and the schema already explains the UUID format and 30-day usability window. With the schema doing all the work, the description contributes nothing extra, so the baseline of 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?

The description reads 'Description of the fields for sending a request:' — a dangling boilerplate fragment that never states what the tool actually does. It does not even restate the name/title, so an agent learns nothing about retrieving Seznam organic SERP results by task id.

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?

There is no when-to-use guidance whatsoever, despite the presence of close siblings such as get_dataforseo_serp_seznam_organic_fetch_html and _regular, and the submit counterpart post_dataforseo_serp_seznam_organic_submit. No context, no exclusions, nothing to infer from.

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